Loading tutorials…
Loading tutorials…
Most of your team will never love the Airtable Grid view — and they should not have to. Interface Designer turns a base into a custom app. This walks the patterns that make non-database users productive.
Who this is forOperators whose team includes execs, vendors, or non-technical contributors who currently avoid the Airtable base because the Grid feels like a spreadsheet. If your sales reps, executives, or external collaborators are screen-sharing screenshots of the base instead of opening it, Interfaces are the fix.
What you'll need
Step 1
Interface Designer is a no-code app builder on top of Airtable data. It lets you build read-and-write apps for specific audiences without exposing the raw base.
Open Airtable → at the top of your base → "Interfaces" tab.
An Interface = a collection of pages, each with elements (charts, lists, record reviews, buttons) that read or write to your base tables.
Interfaces are NOT a different database — they are a UI layer on the same underlying base. Edit a record in the interface, the base reflects the change immediately. Edit it in the Grid view, the interface reflects it within seconds.
Audience patterns: Sales Pipeline Dashboard for sales reps (different from a Sales Director dashboard with management metrics), Content Editor Approval interface (review and approve content without seeing budget data), Client Project Status page (shareable externally with only the client's rows).
Permission scope: interfaces have their own permissions — different from base permissions. You can give a stakeholder access to the interface without giving them access to the underlying base.
Step 2
Interfaces → Start designing → pick from Dashboard / Record Review / Record Summary / Numeric chart starters → customize from there.
Inside the Interfaces tab → "Start designing" → choose from the layout starters: Dashboard (multi-element grid), Record Review (one record at a time, full detail), Record Summary (list + detail), List of records, Form (data entry interface).
Pick "Dashboard" for your first one. Name it ("Pipeline Overview," "Content Performance," "Project Status").
Choose the table this interface will read from. Most interfaces are scoped to one primary table with cross-links to others.
Airtable auto-generates a starter layout — usually a list of records on the left, a record detail panel on the right, plus some summary numbers at the top.
Edit Mode (the toggle top-right) lets you add, remove, and configure elements. Preview Mode shows what users will see.
Step 3
Elements are the building blocks. Pick the right element for each piece of data — list for navigation, chart for trends, number for KPIs, record review for detail.
In Edit Mode → "+ Add element" → element type.
List element: a scannable list of records from a table, filterable. Use for "All open deals," "All published content this quarter."
Chart element (Team+): bar, line, pie, scatter. Configure x-axis, y-axis, group-by, color-by. Use for trend visualization ("Revenue by month," "Content by channel").
Number element: a single big number with a label. Use for KPIs ("Pipeline this quarter: $1.2M," "Content shipped this month: 14").
Record review element: full record detail with inline-editable fields. Use as the "detail panel" of a Dashboard layout. Configure which fields show and which are editable.
Button element: a clickable button that fires an automation. Use for "Approve and publish," "Send proposal," "Mark as Closed Won." Buttons trigger Airtable automations via webhook.
Filter element: lets users filter the page's data without leaving the interface. Use for date range pickers, audience filters.
Step 4
Record review elements are how non-database users edit data without opening the Grid. Pick which fields are editable, which are read-only.
Click a Record Review element → right panel → "Fields."
Toggle each field: Show, Hide, or Show as read-only.
For an Exec interface: show Status, Owner, Amount as read-only; hide internal notes; allow no edits.
For a Sales Rep interface: show all deal fields as editable except Owner (which should be system-set) and any locked Rollup fields (derived data, never edit).
For a Client interface: show only the fields the client should see (project status, milestones, deliverables). Hide internal costs, owner emails, internal notes.
Test by switching to Preview Mode and clicking through. Verify the right fields show edit pencils and the wrong ones do not.
Step 5
Most interfaces have 3-5 pages: an overview/dashboard, a list page, a detail page, an admin page. Use page navigation in the left sidebar.
Add a page: in Interfaces left sidebar → "+ Add page" → start with a layout.
Common pattern: Page 1 = Overview Dashboard (top-level KPIs). Page 2 = List + Detail (browse records). Page 3 = Forms / Inputs (create new records). Page 4 = Admin / Settings (visible to power users only).
Pages can be hidden per user role: in page settings → "Visible to" → restrict to specific user groups.
Cross-page linking: a List element on Page 2 can link to the same record on Page 3 (a Record Review page). Click a row → navigate to the detail page with that record loaded.
Avoid more than 5-7 pages — interfaces should feel focused, not bureaucratic.
Step 6
Interfaces have their own permission model. On Business+ tier, you can share an interface with users who do not have base access.
Top-right "Share" button on the interface → "Share interface."
Add users by email. Set role: Editor (can edit records the interface exposes), Commenter (can comment), Read only (view + filter, no edits).
On Business+ tier, you can share with users who are not collaborators on the base — they see only the interface, never the raw Grid. This is huge for client-facing dashboards and exec views.
Generate a shareable link (Team+): "Create a shareable link" → password-protect optional → restrict by domain optional. Read-only by default.
Audit access quarterly: who has interface access vs base access vs no access? Tidy up departed team members and old clients.
Step 7
The first version of any interface is wrong. Watch how users actually use it; iterate in week 2 and week 4.
Schedule a 15-min "show me how you use this" session with each audience type in week 1.
Watch for: fields they always edit (move to top), fields they never look at (hide), navigation patterns (consolidate), elements they ignore (delete).
Common iterations: too many fields on the Record Review (cut by 30%), wrong default filter on the List (set to "Owner = me" by default), missing summary number at the top (add the KPI they always ask about).
Avoid building an interface for a hypothetical user. Build for the actual user, iterate after first contact.
Common mistakes
Building one giant "everything" interface
What goes wrong: You build an interface with 12 pages and 80 elements that tries to serve sales, marketing, ops, and execs at once. No audience finds it. They all keep using the raw Grid. ~$500-1,500/mo of wasted setup effort plus continued screenshot-driven meetings.
How to avoid: One interface per audience. Sales Pipeline Interface (for reps), Sales Manager Dashboard (for the head of sales), Exec Overview (for leadership). 3-5 pages each, max.
Skipping read-only configuration on Record Review
What goes wrong: An exec accidentally edits the Stage on a deal during their Monday review. Pipeline now shows 'Closed Won' on a deal that is actually in Discovery. Forecast is wrong. Decisions get made on bad data. ~$10-50K of misallocated effort per quarter.
How to avoid: On every Record Review element, audit field-by-field: editable or read-only? Default execs to read-only on everything. Only enable edit on fields where the audience is the rightful owner.
Charts on the wrong fields
What goes wrong: Pie chart on a 50-value Multiple select field = unreadable. Line chart on a Single select with 4 colors = noise. Charts look impressive but communicate nothing. Audience tunes them out.
How to avoid: Use Number elements for KPIs. Use Bar/Line charts only when you have 3-10 categories. For 50+ categories, switch to a Table element with grouping. Less is more.
Sharing interfaces without scoping
What goes wrong: You share an interface with a client. The client sees all your other clients' rows because you forgot to filter. NDA violation, possible legal exposure, loss of trust. Costs vary from $5K reputation hit to a real lawsuit on Enterprise contracts.
How to avoid: On every interface element, scope by user or owner field. On Business+ tier, use Record-level permissions. Test by impersonating a client account before sharing externally.
No iteration after launch
What goes wrong: You ship the interface in week 1, never revisit. By week 8, users have invented workarounds for the parts that do not work — usually back to manual Excel exports. ~$1-3K/mo of wasted seat licenses for an interface no one really uses.
How to avoid: Schedule a 15-min check-in with each audience at week 2 and week 4 post-launch. Iterate on what you see. Then iterate again at month 3.
Recap
Done — what's next
How to set up Airtable views and filters that actually get used
Read the next tutorial
Hand it off
Interfaces are the difference between an Airtable base used by 3 power users and one used by 30 people across the org. A specialist will design and build 2-3 audience-specific interfaces in one engagement — typically $400-800 one-shot. Ongoing interface design as the team grows runs $400-1,200/mo at $14-16/hr.
See specialist rates
Yes — Airtable interfaces are responsive and render on the Airtable mobile app and mobile browsers. For dashboard-style interfaces, mobile usability is good. For Record Review with many fields, mobile is workable but cramped — design for the most-used device first.
Yes — on Team+ tier, create a shareable link for the interface → use an iframe to embed in Notion, Webflow, WordPress, or any HTML page. Pass-through filters via URL parameters (Team+) so you can show different filtered data per embedded location.
Yes — add a 'New Record' button element. Configure which fields show in the create form, defaults, and which fields are required. Submissions write directly to the underlying table. Useful for client-facing intake forms, internal request submissions, etc.
Two paths: (1) On Business+ tier, use the user-as-field permission: invite the client as a user, set Record-level permission 'Owner = current user.' They see only records they own. (2) Build a separate base per client (heavier setup but bulletproof). Path 1 is easier; path 2 is safer.
A view is one way of looking at one table (Grid, Calendar, Kanban). An interface is a multi-page custom app that combines multiple views, charts, KPIs, buttons, and editable records into a designed UX. Views are inside the base; interfaces wrap the base with a presentation layer for specific audiences.
Airtable
Views are why Airtable beats Google Sheets — but most bases have 40 views across 5 tables, half of them stale, none of them documented. This walks the view discipline that keeps a base usable past month three.
Airtable
Airtable automations are powerful, native, and brittle if you wire them wrong. Most bases past 20 automations have 5-8 that silently fail every week. This walks the patterns that hold up.
Airtable
Airtable as a CRM is great for teams under 5 reps with simple sales motions — and terrible past that point. This walks the right structure for the right team, and tells you bluntly when you should be on HubSpot or Pipedrive instead.
Airtable
DIY Airtable is a great idea — until it isn't. This is the honest framework: when the cost of self-managing a base exceeds the cost of hiring help, and how to tell which side you're on.