Loading tutorials…
Loading tutorials…
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.
Who this is forAnyone who has a working Airtable base but realizes the team is creating new views every week without governance. If you cannot find the 'right' view for a daily task in under 10 seconds, this tutorial is for you.
What you'll need
Step 1
Grid (default), Form (data entry), Calendar (date-driven), Kanban (status-driven), Gallery (visual cards), Gantt (timelines), Timeline (multi-bar). Pick deliberately.
Grid view — the default. Use for editorial scanning, sorting, filtering, and bulk-edit work. Every table needs at least one canonical Grid view.
Form view — turns any table into a public or internal data-entry form. Use for intake (brief requests, lead submissions, bug reports). Forms write directly to the table.
Calendar view — records laid out by a date field. Use for content calendars, campaign launch dates, event schedules. Team+ tier supports multiple overlaid date fields.
Kanban view — records grouped as cards by a Single select field. Use for status-driven workflows (editorial pipeline, deal pipeline, support tickets). Drag-and-drop between columns.
Gallery view — records as visual cards, dominated by an image field. Use for asset libraries, design queues, product catalogs.
Gantt view (Team+) — bars on a timeline using start + end date fields. Use for project planning, campaign timelines, dependency tracking.
Timeline view (Team+) — more flexible than Gantt; supports color coding, grouping, multiple records per row. Use for capacity planning, multi-team roadmaps.
Step 2
Open every view in every table. For each, ask: who uses this? When was it last opened? If you cannot answer, delete it.
Open the table → click the view list (left side panel) → expand the full list.
For each view, click and ask: (a) what is this for? (b) who is the audience? (c) is the filter/sort still relevant? (d) when did anyone last open this?
Delete views that have no clear owner or purpose. Right-click → Delete view. Be brutal — every stale view is a tax on the team's ability to find the right view.
Rename surviving views with a convention: "[Audience] [Purpose]" — "Writer — My Content," "Editor — In Review Queue," "Exec — Shipped This Month." Names matter more than people think.
Pin the 4-5 canonical views to the top (drag in the view list). Personal/exploratory views below.
Step 3
Filters are how a view becomes useful. Filter syntax has nuances most users miss — and the differences matter at scale.
Open a view → "Filter" button → "+ Add condition."
Simple filter: Status = "In Progress." Adds one condition.
AND vs OR: by default, conditions are AND. Click the "And" between conditions to flip to OR. Use AND for narrowing (Status = "Draft" AND Owner = "me"), OR for inclusion (Status = "Draft" OR Status = "In Review").
Condition groups: click "+ Add condition group" for nested logic — (Status = "Draft" AND Owner = "me") OR (Status = "In Review" AND Reviewer = "me"). Critical for views that combine "my work" with "work waiting on me."
Dynamic dates: use "this week," "next month," "the past 30 days" instead of hardcoded dates. The filter stays current without manual updates.
Filter by current user: where the audience is the user themselves, use "is current user" on the Owner/Reviewer field. One view serves the whole team.
Empty / not empty: critical for surfacing unfilled fields ("Show me content with no Publish Date set").
Step 4
Sort orders rows. Group creates collapsible sections. Both are view-scoped, both affect how the team scans the data.
Sort: "Sort" button → "+ Pick a field" → ascending/descending. Multi-level sorts (sort by Owner, then by Due Date) work — the first sort dominates.
Group: "Group" button → "+ Pick a field" → ascending/descending. Group by Status (the workflow), Owner (per-rep view), Quarter (forecasting), Channel (distribution).
Within a group, sort still applies. Group by Status, then sort by Due Date within each group — the most urgent draft sits at the top of "Drafting."
Collapsible groups: click the chevron to collapse/expand. For a 500-row table, this is the difference between scanning and drowning.
On Team+ tier, color records by field: "Color" button → pick a Single select field. Visualizes status without filtering.
Step 5
Each view should show 5-8 fields max. Hide everything else. Cluttered views are unused views.
"Hide fields" button (toolbar) → toggle off fields not relevant to the view.
A Writer's view does not need to show Budget. A Manager's view does not need to show Asset Links. Hide what is not relevant.
Drag field order in the view to put the most-used fields leftmost. The team scans left-to-right; design for that.
On a Grid view with 25 fields, hiding 18 of them is normal. Do not feel bad about it — the underlying data is unchanged.
Different views can hide different fields. The "Exec Shipped" view shows Type, Channel, Publish Date. The "Editorial Queue" view shows Status, Owner, Due Date.
Step 6
Personal views are private to you. Collaborative views are shared. Mixing them up causes 80% of "why does my view look different?" confusion.
When you create a view, the icon next to the name indicates type: a single-person icon = Personal; a multi-person icon = Collaborative.
Personal views: your own filters/sorts. Other users cannot see your Personal views. Use for "Owner = me" filters, ad-hoc exploration, drafts.
Collaborative views: shared with all base collaborators. Use for canonical views the team relies on.
Right-click a view → "Change view type" to convert between Personal and Collaborative.
On Business+ tier, lock Collaborative views — anyone can see them, only the lock-holder can change them. Use this on critical views (Exec dashboard, Pipeline Kanban).
Convention: name Collaborative views with "[Audience] [Purpose]." Name Personal views with "(My) [Whatever]" — visually clear which is which.
Step 7
Any view can be shared externally as a read-only URL (Team+ tier). Useful for stakeholders, clients, vendors without giving them a base seat.
Open a view → "Share view" button (toolbar) → "Create a shareable view link."
Configure: read-only (default), include attachments yes/no, password-protect yes/no, restricted to specific email domains yes/no.
Copy the URL. Send to the stakeholder.
The view stays live — changes in the base are reflected in the shared URL within seconds.
On Business+ tier, embed shared views inside Notion, Confluence, or a Webflow site via iframe — useful for client-facing dashboards.
Audit shared view links quarterly: any link with no current owner or expired use case should be revoked. Stale shared URLs are a privacy risk.
Common mistakes
30+ views per table, no documentation
What goes wrong: Team cannot find the 'right' view. New hires take 2-4 hrs to learn which view is canonical for their role. Stale views show wrong data and get cited in meetings. ~4-8 hrs/week of lost productivity per 10-person team — $4-8K/quarter.
How to avoid: Audit and delete. Cap each table at 8-12 collaborative views. Document each in a Base Conventions doc.
No naming convention
What goes wrong: Views named 'View 1,' 'New view,' 'Test,' 'Old kanban (do not use).' Team scans the view list and gives up. Falls back to default Grid. Half the value of Airtable evaporates.
How to avoid: Adopt "[Audience] [Purpose]" naming. Pin the 5 canonical views to the top. Audit monthly.
Filters built on free-text fields
What goes wrong: Status field is Long text instead of Single select. Filter 'Status contains Draft' misses 'drafted,' 'Drafting,' 'DRAFT.' Views show inconsistent data. Reports are wrong by 15-30%.
How to avoid: Filters should target Single select, Multiple select, User, Date, or Linked record fields. Avoid free-text filters for anything you report on.
Personal vs Collaborative confusion
What goes wrong: Manager builds 'Weekly Pipeline Review' as a Personal view. Sales team cannot see it. Manager re-explains in every meeting. Or worse — manager builds it Collaborative, then customizes it during meetings, breaking it for everyone else. ~$500-1,000/quarter of meeting friction.
How to avoid: Default Collaborative for shared meetings. Default Personal for exploration. Lock canonical Collaborative views on Business+ tier.
Sharing edit access on external view links
What goes wrong: Stakeholder accidentally edits or deletes a record from a shared view. No audit trail. Data loss costs hours of reconstruction. In a CRM context, a deleted deal is $5-50K of pipeline gone.
How to avoid: Default shared view links to read-only. Only enable edit on shared links with explicit reason. Password-protect any link with sensitive data.
Recap
Done — what's next
How to set up an Airtable base for marketing without rebuilding it in month two
Read the next tutorial
Hand it off
View governance is the difference between a base the team trusts and one they work around. A specialist will audit your base, kill stale views, build the canonical 5-8 views per table, and document conventions — typically $200-400 for a one-time audit. Ongoing base hygiene runs $400-1,200/mo at $14-16/hr.
See specialist rates
Most healthy bases run 5-12 Collaborative views per table plus a handful of Personal views per user. Past 15 Collaborative views, you almost certainly have duplicates or stale views. Audit quarterly. The right number is 'every view has a clear owner and recent use.'
Filters hide records based on conditions you define (Status = Active). Hidden records (in some views via the right-click menu) are explicitly hidden by ID — useful for one-off cases. Filtering scales; per-record hiding does not. Always prefer filters.
Not directly — each view is scoped to a single table. To see combined data, build Lookup fields that pull values from related tables into one view. For true multi-table dashboards, use Interface Designer (tutorial 6) or a Sync to a separate base on Business+ tier.
Use Form view. Build a Form on the Content (or Briefs, or whatever) table. Share the form URL with the vendor. They submit; the response writes directly to the table. Configure fields shown, required, and prefilled via URL parameters.
You are looking at a Personal view. Personal views are not shared. Convert to Collaborative: right-click the view → 'Change view type.' Other users now see the same filters/sorts. On Business+ tier, lock the view so others cannot accidentally change it.
Airtable
Airtable is fast to spin up and easy to wire wrong. Most marketing bases hit a wall at 3,000 records or 10 linked tables because the schema was built around the first idea, not the second year of data. This walks the base structure that holds up.
Airtable
Most content calendars die in week six because they were built as a list, not as a workflow. This walks the Airtable setup that gives writers, editors, and the CEO each a view of the same data — and stays alive past the first quarter.
Airtable
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.
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.