Every Airtable base eventually outgrows its grid view. You have 4,000 deals, 600 projects, or 12,000 inventory items, and the question you actually need answered — how much revenue closed this quarter, which projects are at risk, what's stocked below reorder point — can't be eyeballed from a table. That's what an Airtable dashboard is for.
This guide covers how to build a dashboard in Airtable using Interface Designer, the native dashboard builder included on every paid plan. We'll walk through the Dashboard layout end-to-end — picking elements, wiring filters, choosing chart types, and the patterns we use on real client builds. By the end you'll have enough to ship a CRM, project, or operations dashboard the same day.
What an Airtable Dashboard Actually Is
An Airtable dashboard is an Interface Designer page that combines summary numbers, charts, filtered record lists, and other elements into a single screen tied to live base data. There's no separate "dashboard tool" — dashboards are just one of the interface layouts Airtable ships, alongside Record Review, Record Summary, and the blank canvas.
Three properties make Interface Designer dashboards different from views:
- They aggregate. A number element can show a SUM, COUNT, AVERAGE, or PERCENTAGE across thousands of records. A view can only show rows.
- They combine sources. One dashboard page can pull from Deals, Activities, and Accounts simultaneously. A view sees one table.
- They have an audience. Dashboards are read-mostly surfaces for executives, clients, or cross-functional partners. The underlying base is for the people editing data.
A good rule of thumb: if a stakeholder is going to open it without editing anything, it belongs in a dashboard, not a view.
Before You Open Interface Designer
The hardest part of dashboard building isn't the interface — it's the base underneath it. Three things to fix in the base before you start dragging chart elements onto a page.
1. Get your linked records right. Charts and rollups depend on relationships. If your Deals table doesn't link to Accounts, you can't chart revenue by account. See Airtable linked records explained if you need a refresher.
2. Add the rollup and formula fields you'll need. Interface Designer can aggregate on the fly, but if you want to chart "deals weighted by probability" or "projects with margin below 20%," create those formula fields in the base first. Charts read from fields — they don't compute new ones.
3. Create the source views. Every chart and list element on a dashboard is backed by a view. Build the views in the base ("Closed Won This Quarter," "Active Projects," "Tasks Due This Week") before opening the interface. You'll thank yourself when you go to wire up the eighth chart.
Step-by-Step: Build Your First Airtable Dashboard
The full path from empty interface to working dashboard takes about 30 minutes once the base is ready.
1. Create the Interface
Click the Interfaces icon at the top of your base. Click Start building. Pick the base you want the dashboard to read from.
2. Choose the Dashboard Layout
Airtable will offer several layouts. For a dashboard, pick Dashboard (formerly called "Blank with elements" in some accounts — same thing). The other layouts (Record Review, Record Summary) are tuned for single-record workflows, not aggregate reporting.
3. Name the Page and Set Permissions
Name it for the audience, not the data — "Sales Pipeline Q3" reads better than "Deals Chart." Under Access, decide who sees it. Workspace members are included by default; you'll add interface-only users in step 8.
4. Drop in Your First Number Card
Number cards are the highest-density element on a dashboard — one statistic per card. From the left panel, drag a Number element onto the canvas. Configure it:
- Source table: pick the table to count or sum.
- Source view (optional): restrict to a filtered view, e.g. "Closed Won — Current Quarter."
- Calculation: SUM, COUNT, AVERAGE, MIN, MAX, or a percentage of records matching a condition.
- Field: the field being summed or averaged (skipped for COUNT).
A standard sales dashboard opens with four number cards across the top: Pipeline Value, Closed Won MTD, Win Rate, Avg Deal Size.
5. Add a Chart
Drag a Chart element from the left panel. Pick the chart type, then the source view and the x-axis/y-axis fields.
| Chart Type | When to Use |
|---|---|
| Bar (vertical) | Comparing discrete categories — revenue by region, tickets by status |
| Bar (stacked) | Same categories broken down by a second dimension |
| Line | Trends over time — MRR by month, signups by week |
| Pie / Donut | Share of total when there are 2–5 categories (not more) |
| Scatter | Two-variable relationship — deal size vs sales cycle |
| Number / Gauge | Single KPI against a target |
Pie charts with eight slices are unreadable — that's the most common mistake we untangle on rescue projects. If you have more than five categories, switch to a horizontal bar chart sorted descending.
6. Add a Filtered List
Drag the List element onto the page. Pick a source view, choose which fields to show, and decide whether records should be clickable to open a detail page. A "Projects at Risk" list under your project dashboard usually shows: Project Name, Owner, Due Date, Status, % Complete.
7. Wire Up Filters at the Page Level
This is the feature most first-time dashboard builders miss. Click the Filter icon at the top of the interface. Add a page-level filter — for example, a Date range picker that filters every element on the page, or a single-select field that lets the viewer pick a region.
Page-level filters cascade to every element that uses the filtered table as its source. You build one dashboard, the viewer gets self-serve filtering, and you don't have to maintain twelve regional copies of the same page.
8. Set Permissions and Publish
Click Publish in the top right. Decide:
- Workspace members — everyone on the workspace sees it automatically.
- Specific people — invite by email; counts as an interface-only seat on Team and above.
- Public share link (Business and Enterprise plans) — anyone with the URL can view. Add a password and restrict to an email domain if the data is sensitive.
For Airtable's authoritative documentation on interface sharing, see the Interface Designer sharing guide.
Five Dashboard Patterns We Use on Every Client Build
These are the layouts that recur across the client reporting dashboards we ship.
CRM / Sales Pipeline Dashboard
Top row: four number cards — Pipeline $, Closed Won MTD, Win Rate, Forecast (weighted). Middle: a stacked bar chart of pipeline by stage, broken down by owner. A line chart of closed revenue by month. Bottom: two lists — Deals Slipping (close date in the past, still open) and Hot Deals This Week (close date next 7 days, probability above 70%).
Project Status Dashboard
Top: number cards for Active Projects, At Risk, Overdue Tasks, Hours This Week. A horizontal stacked bar of projects by phase. A list of projects with red/amber/green status (use a single-select with color). A calendar element showing project milestones.
Operations / Inventory Dashboard
Number cards for SKUs Below Reorder Point, Stock Value, Open POs, Days of Cover. A horizontal bar chart of stock value by warehouse. A list of items below reorder point sorted by days-of-cover ascending — this is the buyer's daily worklist.
Client-Facing Reporting Dashboard
Public-share or interface-user dashboard with no internal data. Number cards for Tasks Completed, Hours Logged This Month, Active Projects, Next Milestone. A chart of completed work by week. A list of upcoming deliverables. Filter by Client at the page level so one dashboard serves every client.
Executive Roll-Up
The hardest dashboard to build and the most-used by leadership. A single page that aggregates every team's KPI: Revenue, Pipeline, Active Customers, NPS, Open Roles, Cash Position. Charts are minimal — one revenue trendline, one customer cohort retention chart. The discipline is brutal: anything that doesn't change the CEO's mind comes off the page.
Charts Element vs Charts Extension: Which One?
Airtable has two ways to make charts and beginners conflate them. They are not the same.
| Feature | Interface Designer Charts | Charts Extension |
|---|---|---|
| Where it lives | Interface page | Inside a base's Extensions panel |
| Audience | Read-only stakeholders | People working in the base directly |
| Filter controls | Page-level filters | Per-extension settings only |
| Public embed | Yes (share link) | Yes (extension embed URL) |
| Drill into source record | Yes | No |
| Chart types | Bar, Line, Pie, Scatter | Same set plus a few advanced options |
The general rule: build dashboards in Interface Designer; use the Charts extension for ad-hoc analysis next to the data. We've covered the extension in more depth in our Airtable extensions overview.
Filters: The Feature That Makes Dashboards Reusable
A dashboard with no filters is just a static screenshot. Interface Designer supports three filter scopes — knowing the difference is the single biggest skill jump in dashboard building.
Element filters are baked into each chart, list, or number card. You set them once when you build the element; the viewer can't change them. Use these for "what this element is fundamentally showing."
Page filters appear as a control bar at the top of the page that the viewer can change. Every compatible element on the page updates when the filter changes. Use these for "the dimension the viewer wants to slice by" — date range, region, owner.
User filters (Business and Enterprise) filter the dashboard based on who is logged in. A salesperson logging in sees only their own deals. A client logging in sees only their projects. This is how you build one dashboard that serves a thousand users without leaking data.
Wire your filters in this order: element filters first (lock down what doesn't change), then page filters (give the viewer their controls), then user filters last (if you need per-user data isolation).
Performance: Keep Dashboards Snappy
Three rules to keep dashboards under two seconds to load.
- Filter at the source view, not the element. A chart pointing at a view filtered to "This Quarter" loads faster than a chart pointing at the full table with a 2026-Q3 condition layered on top.
- Pre-compute heavy aggregations. If you need "average customer lifetime value" and that's a 20-step calculation, use an automation or script to write a snapshot field nightly, and chart that field instead of recomputing live.
- Cap elements per page at 12. Above that, Airtable users have reported visible lag, particularly on tables over 50,000 records. Split content across multiple pages and link them in the navigation.
Common Mistakes
Five issues we see on most dashboard rescue projects.
Building dashboards before the base schema is right. If your Deals table doesn't link to Accounts, no amount of chart configuration will produce a clean "Revenue by Account" view. Fix the schema first, then the dashboard takes 30 minutes instead of three days.
Putting too many elements on one page. Twelve elements is the comfort ceiling. Above that, the page slows down, the viewer's eye doesn't know where to land, and you'll spend more time maintaining the page than people spend reading it. Split into multiple pages with clear navigation labels.
Charting lookup fields that return multiple values. A lookup that returns "Acme Corp, Initech, Hooli" gets counted as three data points by the chart engine. If you want one value per record, swap the lookup for a single-text or single-select rollup with ARRAYJOIN.
Forgetting to set the source view filter. The chart will silently include records you meant to exclude — archived deals, test data, draft records. Always point charts at a curated view, not the entire table.
Skipping page-level filters. Without them you end up duplicating the dashboard for every region, every product line, every quarter. One properly-filtered dashboard replaces six copies and stays in sync forever.
Troubleshooting Dashboard Issues
| Symptom | Likely Cause | Fix |
|---|---|---|
| Chart totals don't match the table | Source view has an unexpected filter | Open the source view in the base; check its filter conditions |
| Number card shows "0" or blank | Field selected is a lookup or doesn't exist on the view's records | Switch to a formula or rollup field that produces a single number per record |
| Page loads slowly | Too many elements or unfiltered table sources | Cap at 12 elements, point charts at filtered views |
| Public share link returns "not found" | Public sharing is disabled on this plan or workspace | Public dashboards require Business or Enterprise; otherwise use email invites |
| Filter doesn't apply to a chart | The chart's source table differs from the filter's table | Add a same-table source or use a synced/linked table on both sides |
| Viewer sees data they shouldn't | No user-level filter configured | Add a user filter that matches the logged-in user to a field on the record |
Where to Go Next
Once you have a working dashboard, the natural next steps are automating the data feeding it and connecting it to external tools. Our Airtable automation guide covers the triggers and actions that keep dashboard data fresh without manual touch. The client reporting dashboards tutorial goes deeper on the multi-client patterns and user filters introduced above.
For the underlying mechanics, the Interface Designer guide covers every element type — including the record review and summary layouts we didn't have space for here. Airtable's official Interface Designer documentation is worth bookmarking for permission edge cases.
When the team needs charts that Interface Designer can't produce — multi-axis time series, geographic heat maps, advanced statistical visualisations — that's the point to connect Airtable to a dedicated BI tool. We cover that path in how to connect Airtable to Power BI.
