Airtable Interfaces: What They Can and Can't Do

Interface Designer is the single most useful feature Airtable has shipped since linked records. It turns a relational database into something a non-technical team member can actually use — dashboards, record review pages, forms, calendars, all built without leaving Airtable. For internal teams who want a frontend on top of their data, it's free on paid plans and genuinely good at what it does.

It's also the feature that most teams misjudge the limits of. Airtable's own community managers describe Interfaces as "more inclined towards internal business tools, not consumer-facing apps," and yet the most common reason builders evaluate Interfaces is to use them as exactly that — client portals, vendor apps, customer-facing tools. Some of those use cases work; many don't. Knowing where the line falls is the difference between shipping in a week and rebuilding in three months.

This guide is for builders, ops leads, and founders who already use Airtable as a database and are deciding whether Interfaces (free), the Portals add-on, or a third-party frontend is the right next step. It walks through what Interface Designer can do well, where the limits show up, what Portals add and don't, and where Noloco fits as the most common third-party frontend choice for service businesses pairing Airtable with branded client experiences. The goal isn't to talk you out of Airtable Interfaces — they're the right answer for plenty of use cases. It's to help you pick the right frontend layer for the use case in front of you.

TL;DR

• Airtable Interfaces are a free feature on every paid plan. They let Creators build dashboards, record review pages, forms, and custom layouts without leaving Airtable. For internal teams, they're excellent.
• Interfaces are designed for internal users. Airtable's own community confirms they prioritize "speed of development over visual polish" and "functional consistency over brand alignment." That's the right tradeoff for ops dashboards. It's the wrong tradeoff for client portals.
• External access has three paths: public read-only links (free, no edits), inviting users as Airtable editors (~$20/seat/mo each), or the Airtable Portals add-on (~$8/guest/mo, 15-guest packs from $120/mo). Each path has tradeoffs that compound at scale.
• The biggest gaps for client-facing use: no custom domain, limited branding (logo on sign-in only on Business+), no field-level permission control, hard 50-interface-per-base cap, and partial mobile coverage.
• For agencies, service firms, and any team where client experience is part of the product, Noloco is the most commonly chosen third-party frontend because it adds full branding, custom domains, granular permissions, native mobile apps, and bundle-seat pricing on top of Airtable's data layer.
• Honest test: if your users have your company email domain and won't notice the Airtable branding, Interfaces are enough. If your users are external clients who'll judge your service partly by how the portal looks and works, Interfaces alone usually aren't.

What can Airtable Interfaces actually do?

Interface Designer ships with every Airtable workspace and is included on Free, Team, Business, and Enterprise Scale plans. Base collaborators with Creator permissions can build interfaces; all base collaborators can view and interact with published interfaces at the same access level as their base permissions; and "interface-only" collaborators can view and interact with interfaces without seeing the underlying base. The mental model is simple: interfaces are a curated view layer on top of your raw data.

Within those constraints, Interface Designer covers a useful range of UI patterns:

What Interfaces are genuinely good at

• Internal dashboards — utilization heat maps, project status boards, content calendars, ops snapshots.
• Record review workflows — a sales lead pipeline where reps see one lead at a time with relevant context.
• Filtered list views — "my projects," "open tickets assigned to me," "this week's deadlines."
• Lightweight forms — internal request submissions, simple intake flows.
• Read-only public dashboards — a live status page or executive dashboard shared via public link.

How Interface permissions work

Interface permissions sit on top of base permissions. The Filter by setting on each interface page controls record visibility — you can show all records, specific records based on conditions, or only records belonging to the viewer ("viewer's records," matched via a user or email field on each record). Field visibility is controlled separately by what fields you include in the interface layout.

This sounds flexible until you try to build a portal where different roles need to see different fields on the same record. Interface permissions are largely page-level. Per-field control across roles isn't a first-class feature — you typically end up creating duplicate interfaces with different field configurations, or duplicate pages within a single interface, which is fine until you're maintaining ten of them.

Where do Airtable Interfaces hit their limits?

The limits aren't bugs — they're consequences of Interfaces being designed for internal users on the same workspace. The question for builders is whether the use case in front of them sits inside or outside those design choices. Below are the ten limits that consistently come up when teams try to use Interfaces for client-facing work.

1. The internal-first design

Interfaces assume your users are part of your Airtable workspace. External users have to either be added as paid editors (~$20/month each), invited as portal guests via the paid Airtable Portals add-on, or restricted to read-only public link viewing. None of those paths is what you'd design from scratch if your goal were a polished external experience.

2. Branding can't be removed

There is no option to remove Airtable's branding from Interfaces. The Airtable logo and "powered by Airtable" appear in the interface chrome. The Portals add-on lets you customize the sign-in page on Business plan and above (logo + image), but everything past the login screen is still Airtable's design system. For a client portal where branding is part of the service experience, this is a real constraint.

3. No custom domain support

Portals run on airtable.com URLs. There's currently no way to point your portal to portal.youragency.com. Airtable representatives have confirmed this in community threads, and it's one of the most consistently requested features that hasn't shipped. For agencies whose clients log in regularly, the URL matters.

4. Limited theming

Interface Designer restricts you to Airtable's design system. You can set basic organization branding (logo, image), but there's no control over colors, fonts, borders, or backgrounds beyond defaults. Builders who want a portal that looks like an extension of their agency website typically end up using a third-party tool because the visual customization simply isn't there.

5. Field-level permissions are weak

You can hide records (page-level filters) and you can omit fields from a layout. What you can't easily do is show the same record with different field visibility for different roles — a junior consultant seeing project data without rate cards, a client seeing their project without internal notes. Workarounds exist (multiple interfaces, multiple pages), but they don't scale beyond a handful of role types.

6. External users see each other by default

This one catches a lot of agencies off guard. When you share an interface with multiple users, by default they can all see the names and email addresses of every other user with access via the "Share" → "Manage Access" menu. For a portal where each client should be invisible to the others, this is a privacy problem. Airtable did add an admin-level setting on Business and Enterprise Scale plans to hide external collaborators from each other, but it's an admin-panel setting, not the default.

7. The 50-interface-per-base cap

Each base supports a maximum of 50 interfaces. For most internal use cases this is plenty. For agencies trying the "one interface per client" pattern, this hits hard — the moment you cross 50 active clients, you're forced into a multi-base architecture or a different frontend tool entirely. The cap doesn't lift with higher plans.

8. Edit access requires Airtable accounts

Public interface links are read-only. For external users to edit records (submit updates, approve work, modify their own data), they either need to be invited as Airtable editors (becoming paid seats) or accessed through the Portals add-on. There's no middle ground where an external user creates a lightweight account and edits without becoming an Airtable editor.

9. Mobile coverage is partial

Most interface page layouts are mobile-responsive in Airtable's mobile browser experience. The blank page layout type — the most flexible option for custom UI — is the least mobile-friendly. There's no native mobile app for end users of an Airtable interface; everything routes through the browser. For a client portal where clients check status from their phone between meetings, this is a meaningful UX gap.

10. Public links are read-only only

If you want to share an interface publicly without authentication, the public link is read-only. Public users can view, filter, and search, but cannot create, edit, or delete records. For lead capture pages, public submission flows, or any "prospect submits info, we follow up" pattern, public interface links don't work. You either need Forms (which are limited) or a third-party frontend that supports public-facing apps with submission.

Does the Airtable Portals add-on solve the gaps?

Airtable Portals went generally available in 2024 and addresses some of the external-access limits of Interfaces, but not all. Portals are a paid add-on on top of Team or Business plans, priced at roughly $120/month for 15 guests on Team or $150/month on Business, with volume discounts at higher seat counts. Here's what they fix — and what they don't.

What Portals add

• External user access without per-seat editor pricing — guests are billed at ~$8/month each instead of ~$20.
• A custom sign-in page (logo and image) on Business plan and above.
• The ability for external users to edit data without needing their own Airtable account.
• Admin-panel controls for hiding external collaborators from each other on Business+.
• Invitation by email or share link for portal guests.

What Portals don't fix

The architectural limits of Interface Designer carry over. Portals are a wrapper that changes who can access an interface and how they log in — they don't change what an interface can be.

• Branding is still mostly Airtable's. Custom sign-in is the only branded surface; everything past login is the Airtable design system.
• No custom domain support.
• Field-level permissions don't get more granular.
• The 50-interface-per-base cap still applies.
• The guest definition is strict — portal guests must have a different email domain than your workspace, so Portals can't be used as a workaround for reducing internal seat costs.
• Mobile experience is the same as regular Interfaces.
• At scale (50+ external users), the per-guest pricing starts adding up faster than flat-rate third-party portal tools.

In practice: Portals are a good fit for teams with 5–20 external users who want a quick external access layer without changing tools. They're a less good fit when external users are central to the product (agencies running client portals as part of their service), when branding needs to feel agency-native, or when client counts are growing fast.

Where does Noloco fit as the frontend layer for Airtable?

When teams hit the limits of Interfaces and find Portals doesn't fully close the gap, the most common third-party choice for service businesses is Noloco. Noloco connects directly to Airtable as a data source and adds a frontend layer specifically designed for the client-facing use cases Airtable's native tools don't fully serve. Even Airtable consultants in the community openly recommend Noloco when client portal needs exceed Interface Designer's capabilities.

The architectural pattern is straightforward: Airtable stays as the data layer (or, for teams that prefer a simpler stack, Noloco's native database replaces it). Noloco handles the frontend — branding, permissions, custom domains, mobile, public access. The two systems sync in real time. Builders typically describe the combination as "Airtable's flexibility + a real frontend."

What Noloco adds on top of Airtable Interfaces

Full branding throughout, not just the sign-in page. Where Portals lets you customize the sign-in screen on Business+, Noloco's app builder puts your logo, colors, typography, and layout choices on every page — navigation, dashboards, record views, mobile screens. The portal feels like an extension of your service, not a database with a logo on the door.

Custom domain support. Run the portal at portal.youragency.com instead of an airtable.com URL. For agencies pitching a portal as part of their service, this is the difference between a SaaS handoff and a credible service offering.

Field-level permissions. Where Interface permissions are largely page-level, Noloco supports granular permissions at the table, page, record, and field level. Different roles can see different fields on the same record — internal team sees rate cards and notes, clients see project status and deliverables, and you don't need to maintain duplicate interfaces to make it work.

Drag-and-drop layout flexibility. Interface Designer's blank page layout is the only fully customizable option, and it's the least mobile-friendly. Noloco's app builder gives you drag-and-drop layout across every page type — dashboards, lists, detail views, forms — with full mobile responsiveness baked in.

Bundle pricing instead of per-guest billing. Airtable Portals charges roughly $8 per guest per month. Noloco's pricing bundles internal team and client portal access in a predictable plan structure — inviting more clients doesn't trigger a price increase. For agencies with growing client rosters, this turns client portals from a pricing variable into a fixed cost.

Native mobile apps. Where Airtable interfaces route through the browser with partial layout coverage, Noloco mobile apps ship as native iOS and Android, with the same UI and permissions as the web app. Clients install the app, log in once, and check status from their phone.

Public-facing apps with login control. Where Airtable public links are read-only, Noloco public access lets you build apps where some pages are public, some require login, and external users can submit data without needing third-party accounts. Lead capture, prospect onboarding, feedback portals — use cases Interface public links can't serve.

Workflow automation beyond Airtable. Both platforms have native automations. Noloco adds direct integrations with Zapier, Make, and n8n for orchestration that goes beyond Airtable's automation engine — useful when your workflow touches HubSpot, Stripe, Slack, or other tools alongside the Airtable database.

No interface cap. Where Airtable bases hit a 50-interface ceiling, Noloco doesn't impose a cap. The one-portal-per-client pattern stays workable as your client roster grows past 50.

Airtable Interfaces vs Airtable Portals vs Noloco: side-by-side

The matrix below scores all three options against the dimensions that typically drive the choice. The honest read: Interfaces are the right answer when the experience is internal-first, Portals add some external access at the margin, and Noloco is the right answer when the experience is client-facing in a meaningful way.

Which frontend should you actually use?

The right choice usually comes down to the use case rather than a universal preference. Below is the practical decision matrix.

Stay on Airtable Interfaces alone if...

• All your users are inside your workspace and have your company email domain.
• Your portal needs are internal — ops dashboards, internal CRMs, content calendars, project tracking.
• You don't need custom domains, full branding, or field-level permission control.
• Your team is small enough that the 50-interface-per-base cap won't hit.
• Public sharing is read-only or simple form submission — nothing requiring authenticated external edits.

Add Airtable Portals if...

• You have a small number of external users (5–20) who need to edit data.
• You're already on Business plan and the per-guest pricing isn't a constraint.
• You can live with Airtable's design system on every page past the sign-in screen.
• You don't need custom domains or field-level permissions.

Move to Noloco if...

• Client experience is part of your service — the portal needs to feel branded, polished, and agency-native.
• You need custom domain support.
• Different user roles need to see different fields on the same record.
• Your client roster is growing — you don't want client count to be a pricing variable.
• Mobile experience matters and you want native iOS/Android.
• You're hitting (or about to hit) the 50-interface-per-base cap.
• You need public-facing apps with mixed authenticated and public access.

Final thoughts

Airtable Interfaces are an honest free feature that does exactly what they were designed to do: turn an internal database into something a non-technical team member can actually use. For internal teams, dashboards, ops tools, and lightweight forms, Interfaces (and Portals at the margin) are the right answer most of the time.

The mismatch starts when builders try to use Interfaces as a client-facing product surface — a polished portal, a branded customer experience, an external app where the look and feel is part of the offering. Airtable's own community managers are upfront that Interfaces aren't built for that. The limits aren't going to be solved by a future update to Interface Designer because the design intent is somewhere else: speed of internal iteration, not pixel-perfect external polish.

This is exactly the gap third-party frontend tools fill, and it's the reason the "Airtable as data layer + a real frontend on top" pattern has become standard for service businesses. Among those frontend options, Noloco is the most common pick for agencies and service firms because the things service firms care about most — branded client experience, granular permissions, custom domains, native mobile, predictable pricing — are exactly where Interfaces hit their limits. Keep Airtable for what it's great at. Add Noloco for what it's not.

FAQ

What are Airtable Interfaces?

Airtable Interfaces are a feature of Airtable's Interface Designer, included on all paid plans, that lets builders create curated views of their base data — dashboards, record review pages, forms, calendars, blank custom pages — without leaving Airtable. They sit on top of your base and are designed for internal team members. Base collaborators with Creator permissions can build them; viewers and interface-only collaborators can use them at the same access level as their base permissions.

Are Airtable Interfaces free?

Interface Designer is included at no extra cost on all Airtable plans, including the Free plan. There's no separate fee to build or use interfaces. What is paid is the underlying Airtable plan ($0–$45/editor/month) and the optional Airtable Portals add-on (~$120/month for 15 external guests on Team plan, ~$150/month on Business).

Can I use Airtable Interfaces as a client portal?

Technically yes, but with significant caveats. Airtable's own community describes Interfaces as "more inclined towards internal business tools, not consumer-facing apps." The main limits for client portal use: Airtable branding can't be removed, no custom domain support, field-level permissions are weak, the 50-interface-per-base cap, and external editors either need their own Airtable accounts or the paid Portals add-on. For lightweight read-only client dashboards, Interfaces work. For full branded client portals, most agencies pair Airtable's database with a third-party frontend like Noloco.

What's the difference between Airtable Interfaces and Airtable Portals?

Interfaces are the underlying view-builder — free on all paid plans, designed for internal users. Portals are a paid add-on on top that changes who can access an interface and how they log in. Specifically, Portals let external users (with a different email domain than your workspace) sign in as guests and edit data without needing their own Airtable accounts. The interface itself is the same; Portals add an external login layer with custom sign-in page customization on Business plan and above.

Why are Airtable Interfaces limited for external users?

By design. Airtable Interfaces were built around the assumption that users are part of the same workspace. Several practical limits flow from that: Airtable branding can't be removed, custom domains aren't supported, public links are read-only only, edit access requires either an Airtable account or the Portals add-on, and external collaborators can see each other's names/emails by default unless an admin enables a hide-external setting on Business+. None of these are bugs — they're consequences of the internal-first design intent.

What's the best alternative to Airtable Interfaces for client portals?

For agencies and service businesses, Noloco is the most commonly chosen alternative. It connects directly to Airtable as a data source and adds the things Interfaces don't: full branding, custom domains, granular field-level permissions, native mobile apps, public-facing app support, and bundle-seat pricing instead of per-guest billing. Other options builders evaluate include Softr, Stacker, and Pory — each with their own focus. Noloco is most often picked when the use case is service-business client portals specifically.

How many interfaces can I build per Airtable base?

Each Airtable base supports a maximum of 50 interfaces. This is a hard cap and doesn't scale up with higher plans. For most internal use cases, 50 is more than enough. The cap becomes a problem when builders try to use a one-interface-per-client pattern — the moment you cross 50 active clients, you have to either switch to a multi-base architecture, consolidate clients into shared interfaces with permission filters, or migrate to a frontend tool without the cap.

Do Airtable Interfaces work on mobile?

Most interface page layouts are mobile-responsive in Airtable's mobile browser experience. The blank page layout type — the most flexible option for custom UI — is the least mobile-friendly. There's no native mobile app for end users of an Airtable interface; everything routes through the browser. For client portals where users check in from their phone regularly, the partial mobile coverage is one of the more common reasons teams add a third-party frontend with native mobile apps.

Related resources

Continue exploring how to architect Airtable for client portals and external apps.

Give Airtable a frontend designed for clients.

Noloco connects directly to your Airtable bases and turns them into branded client portals, internal apps, and customer-facing tools — with field-level permissions, custom domains, native mobile apps, and bundle pricing that doesn't penalize you for inviting more clients. Keep Airtable as the database. Replace Interface Designer for everything client-facing.

Book a demo →