Airtable Permission Levels: Which Role Should Staff Get?

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for Airtable Permission Levels: Which Role Should Staff Get?
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for Airtable Permission Levels: Which Role Should Staff Get?

On a small team, give one or two people Owner, whoever builds bases Creator, staff who update records Editor, and people who only look Read-only, which is free. Give outsiders interface-only access to the screens they need. Workspace access overrides base access because the higher level wins.

The Complete Excel Course with AI Integration

From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.

By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner

Buy now

The level worth thinking hardest about is Commenter. On the Team plan it is not a cheap middle option: Airtable's plans overview lists commenters as billable seats, the same $20 a month billed annually as an editor, while read-only collaborators cost nothing. (Its billable-collaborators page names only owners, creators and editors, so check your billing page after the first invite.) For each person, the real question is whether they build things, change data or only look.

The role-by-role table for a nine-person physiotherapy clinic

Here is a filled-in plan for an illustrative clinic with nine people and two bases: Clinic operations (enquiries, class bookings, follow-up calls, stock) and Finance (invoices and supplier bills). Clinical records live in the clinic's dedicated software, not in Airtable.

PersonWhere access is grantedLevelWhy this levelSeat on Team?
Clinic ownerWorkspaceOwnerBilling, plan changes and granting Owner are Owner-onlyYes
Practice managerWorkspaceOwnerAirtable recommends two owners, so a holiday or departure never locks you outYes
Senior physio who builds forms and interfacesClinic operations baseCreatorAdding fields, tables, automations and interfaces needs CreatorYes
Two receptionistsClinic operations baseEditorThey add and update enquiries and bookings all dayYes, two
Three physiosOne interface onlyInterface-only EditorThey tick off follow-up calls on one screen and never need the tablesYes, three
Freelance bookkeeperFinance baseRead-onlyChecks figures and downloads CSVs; edits nothingNo

That is eight paid seats for nine people: 8 × $20 = $160 a month billed annually, or 8 × $24 = $192 billed monthly. The bookkeeper costs nothing. Nobody below the practice manager can touch billing, and only three people can change the structure of a base.

Two things in the table are deliberate. Nobody except the owners has workspace-level access, because workspace access applies to every base in the workspace, Finance included. And the physios are interface-only rather than base Editors, so they see one screen of follow-up calls instead of every enquiry in the clinic.

What can each Airtable permission level do?

Airtable's permission levels differ mainly in what people can change: Owners and Creators build, Editors add and edit records, Commenters comment and Read-only people look.

Airtable publishes base permissions as a grid. The rows that matter most for a small team:

Action in a baseOwner / CreatorEditorCommenterRead-only
Add, edit or delete recordsYesYesNoNo
Comment on recordsYesYesYesNo
Add, delete, rename or change fieldsYesNoNoNo
Add, delete or rename tables, import CSVs as tablesYesNoNoNo
Create or change automationsYesNoNoNo
View automation configurationsYesYesYesYes
Build or publish interfacesYesNoNoNo
Edit records through an interfaceYesYesNoNo
Lock a view, or remove a lockYesNoNoNo
Create view share linksYesYesNoNo
Create collaborator invite links, rename the baseYesNoNoNo
Invite people at or below their own levelYesYesYesYes
Download CSVs of a view, print, copy dataYesYesYesYes

Three rows surprise people. Everyone, read-only included, can invite others at or below their own level, so an Editor can add another Editor and, on Team, another paid seat. Everyone can view automation configurations, so a read-only freelancer can read the email addresses, conditions and message text inside your automations. And everyone can download a view as a CSV, so Read-only means "can't change", not "can't take a copy".

At workspace level the extra powers are few: Owners and Creators can add, remove, reorder and move bases and rename the workspace; only Owners can change billing, upgrade the plan or grant Owner. If your bases use AI field agents, add one more line: only Owners and Creators can change an agent's instructions or model, while Editors and above can trigger runs that spend the workspace's credits. The tutorial on summarising and tagging quote requests with field agents shows why that split matters.

Should you grant Airtable access at workspace or base level?

Airtable keeps workspace and base permissions separately, and your effective permission on a base is the higher of the two, so grant access at base level unless someone needs the whole workspace. A Creator on the workspace who is set as Editor on one base is a Creator in that base and in every other base in the workspace.

The trap, as it plays out in a clinic: the practice manager invites a new receptionist to the workspace as Editor during a busy week, because that's the first share button she finds. Later she sets the receptionist to Read-only on the Finance base, believing that limits her. It doesn't. The workspace Editor permission wins, so the receptionist can edit invoices. The clue was an invoice amount that changed, and the record history showed the receptionist's name on an edit she didn't remember making while tidying a view.

The rule that prevents it: grant access at base level for everyone except the owners, and check each person's workspace permission before relying on a base-level restriction. The workspace share panel lists who has workspace access, and in a base's share panel each person's level appears beside their name.

How does interface-only access work in Airtable?

Interface-only access in Airtable lets a person use the screens they are invited to without seeing the base underneath. An interface is a custom screen built on a base: a list of today's follow-ups, a form, a dashboard. Interface-only collaborators see the interfaces they're invited to and not the base underneath, and their status appears as "Interface access only" in the share panel. Inside an interface they can be:

  • Viewer: sees the interface; no comments, no edits. Not billable.
  • Commenter: sees and comments; can't edit records or submit forms in the interface. Billable on Team and, by Airtable's interface page, on self-serve Business too.
  • Editor: edits records and, where enabled, adds and deletes records and submits forms. Billable.

For the physios, the senior physio (as Creator) builds a "Follow-ups due" interface: a list of patients due a call, with Called on and Outcome editable and everything else read-only. Each physio is invited by email to that interface only. Interfaces can only be shared with verified Airtable accounts, and sharing an interface separately from its base needs a paid plan.

Two cautions from Airtable's own interface permissions page. To limit an existing base collaborator to certain interfaces, you must first remove their base and workspace access, then re-invite them interface-only; leaving their base access in place leaves them in the whole base. And the interface selector in the "Invite via link" dialog does not restrict a link to one interface, so invite by email when it matters.

For clients or patients rather than staff, Airtable sells Portals as an add-on, priced from $120 a month for 15 guests on Team. Whether that beats a separate front end is covered in Airtable's Portals add-on against Softr or Glide.

How do you lock Airtable fields and tables without changing anyone's level?

Airtable's field and table editing permissions let Owners and Creators decide who can edit a field's values, and who can create or delete records in a table, without changing anyone's level. Airtable lists them on Team, Business and Enterprise Scale; field visibility rules inside interfaces, which hide fields from some viewers, need Business or Enterprise Scale. If you'd read that field permissions are Business-only, that is no longer the case for editing permissions.

To set one, open the field's menu and choose Edit field permissions, then choose who may edit from the dropdown under "Who can edit values in this field?". For tables, Edit table permissions controls who can create records and who can delete them. Filled-in examples for the clinic:

Field or tableWho may editWhy
Enquiries: Fee quotedPractice manager onlyReceptionists read it to patients; only one person sets it
Enquiries: SourceReceptionists and upSet once at first contact, used for marketing reports
Follow-ups: OutcomePhysios (through the interface) and upOnly the person who made the call records the result
Follow-ups table: delete recordsOwners onlyA deleted follow-up is a patient who never gets called

Know the limits. These permissions control values, not visibility: everyone with access can still see a locked field. They don't control a field's configuration either (its name, type or select options), which stays with Owners and Creators. They apply wherever edits happen, including interfaces, the mobile apps, extensions and the API, so a locked field stays read-only in an interface even when it looks editable. Commenters can't edit values whatever you set, and formula, lookup and rollup fields can't be edited by anyone directly.

What should you check before inviting anyone else to Airtable?

Before inviting anyone else to Airtable, work through twelve checks, once when you set up the workspace and again whenever someone joins or leaves. Each check says why it matters and how to confirm it. The ticks show the clinic's first run.

Ownership

  1. Two Owners, both reachable. Why: only Owners change billing and grant Owner. Verify: the workspace share panel shows two Owners. Clinic: done.
  2. Creators listed by name, three at most for a small team. Why: Creators change fields, automations and AI agent instructions. Verify: each base's share panel. Clinic: one Creator plus the two Owners.
  3. A written note of who built each automation. Why: if the builder leaves, someone must know what each one sends. Verify: automation descriptions name an owner. Clinic: added for all four automations.

Access

  1. Nobody below Owner has workspace access. Why: workspace access overrides every base. Verify: the workspace share panel lists only Owners. Clinic: one receptionist moved from workspace to base level.
  2. Each person's level matches what they do this month. Why: levels drift upwards. Verify: compare the share panel with the role table. Clinic: matched.
  3. Look-only people are Read-only, not Commenter. Why: on Team a commenter is a paid seat. Verify: no Commenters unless they genuinely discuss records. Clinic: bookkeeper is Read-only.
  4. Interface-only staff have no leftover base access. Why: base access shows them everything. Verify: they appear as "Interface access only". Clinic: three physios confirmed.

Data

  1. Money and identity fields locked. Why: one person should own fees and contact details. Verify: Edit field permissions on each. Clinic: Fee quoted locked.
  2. Key views locked. Why: Editors can change shared views, and a removed filter changes what everyone sees. Verify: the lock icon on each team view. Clinic: four views locked.
  3. Nothing sensitive inside automation messages. Why: every level can view automation configurations. Verify: read each automation as if you were the bookkeeper. Clinic: one email template trimmed.

Money and leavers

  1. Invites controlled. Why: anyone can invite at or below their own level, and on Team that can add a seat. Verify: if your plan shows the toggle "Restrict adding new collaborators to this workspace, its bases, and its interfaces" in the account overview, turn it on; Airtable's page ties parts of this control to Business. Otherwise review the bill monthly. Clinic: monthly review.
  2. A leaver routine. Why: billing is per workspace, so someone still Editor on one forgotten base still uses a seat. Verify: search every base's share panel for the leaver's name. Clinic: written into the leaver checklist.

How do you settle a new starter's Airtable level?

You settle a new starter's Airtable level by answering five questions in order and stopping at the first yes. The table and checklist cover the team you have; these cover each new person:

  1. Will they change fields, tables, automations, interfaces or AI agent instructions? Creator, on the one base where they build. If the honest answer is "occasionally", keep them an Editor and have a Creator make the change.
  2. Will they add or change records most days, across a whole base? Editor, granted at base level.
  3. Will they change records, but only on one screen or for their own work? Interface-only Editor on that interface.
  4. Do they need to discuss records without changing them? Commenter, accepting that on Team it is a paid seat. Often a comment in your chat tool does the same job for free.
  5. Do they only need to look, or to download figures? Read-only, or interface-only Viewer, or a view share link if they don't need an account at all.

Run it for an illustrative new part-time sports therapist joining the clinic. She won't build anything (no to 1). She doesn't work across the whole base (no to 2). She does record her own follow-up outcomes (yes to 3), so she becomes an interface-only Editor on "Follow-ups due", a ninth paid seat at $20 a month billed annually. Had she only needed to see the class timetable, a view share link would have done it at no cost and without an account.

Write the answer into your role table the day she starts, along with the date, so the next review of check 5 has something to compare against.

If you want help deciding who on your team needs which level, I offer one-to-one AI consultations for small businesses.

How much does the Airtable seat bill change with permission levels?

Choosing Read-only instead of Commenter for a bookkeeper saves one billable seat in this illustration of nine people on Team at $20 a seat a month billed annually. The same nine people, three ways:

ApproachBillable seatsMonthly (annual billing)Monthly (monthly billing)
Everyone invited to the workspace as Editor9$180$216
Role table above, bookkeeper as Commenter "to be safe"9$180$216
Role table above, bookkeeper Read-only8$160$192

The saving from the role table is modest, $240 a year in this illustration. The bigger gains are the ones the bill doesn't show: the bookkeeper can't change an invoice, physios don't see every patient enquiry, and nobody can rename a field that three automations depend on. If you're weighing a move to Business at $45 a seat billed annually ($54 monthly) for visibility rules, user groups and admin controls, remember it needs a private email domain and that Airtable lists commenters as non-billable there. Airtable Team versus Business sets out what else changes.

Seat changes have timing rules worth knowing before you tidy up. On monthly billing, a collaborator added mid-period appears as a prorated charge on the next invoice; on annual billing you're charged a prorated amount for the rest of the term. Removing someone mid-cycle doesn't reduce the current invoice; the seat count drops at renewal.

If tracking seats and costs in a spreadsheet is the slow part, try The Complete Excel Course with AI Integration on Coding Liquids.

Where do small teams' Airtable permissions go wrong?

Small teams' Airtable permissions most often go wrong through temporary staff who keep a paid seat, people removed from one base but still billed for another, and workspace access overriding a base setting.

The temp who became a permanent seat

A receptionist covering a busy month invites a temp to the Clinic operations base as Editor, which she is allowed to do because it is her own level. The temp leaves after four weeks; nobody removes them. Six months later the practice manager reconciles the bill and finds a ninth seat, prorated in from the day of the invite. The fix is the leaver routine in check 12, and the invite control in check 11.

Removed from one base, still billed for another

A physio leaves and is removed from the "Follow-ups due" interface, but an old invitation to a stock-count base still makes them an Editor there. Because billing is per workspace, they keep using a seat until they have no billable access anywhere in the workspace. Search every base, not just the main one.

One Owner, on holiday

The only Owner is away when the card on the account expires. Nobody else can change billing. A second Owner, as Airtable recommends for larger teams, would have covered it, and costs nothing extra if that person already has a seat.

If you're handing a base over from someone who built it for you, the ownership and access checks above overlap with what to check when an Airtable consultant hands over, and for a first build of the tables themselves, setting up an Airtable CRM for a service business starts from scratch.

Airtable permissions: questions small teams ask

Can a staff member see a base without being charged a seat?

Yes, as Read-only. Airtable lists read-only workspace collaborators as included on Team and Business, along with form submissions and share links. Interface-only viewers aren't billable either. A read-only person can still comment nowhere and edit nothing, so use it for people who only need to look, such as a bookkeeper checking figures.

Who can change field agent instructions and models?

Only Owners and Creators. Editors and above can trigger an agent's runs, which spend the workspace's AI credits, but they can't rewrite its instructions or switch it to a more expensive model. That makes Creator a level to hand out sparingly in any base that uses AI fields.

Does every collaborator need an Airtable account?

Base and interface collaborators do: interfaces can only be shared with verified Airtable accounts. People outside the team who only submit information can use a form instead, and people who only look can use a view share link. Neither needs a seat or, for the share link, an account.

Do Business-plan permission features work with a Gmail address?

Business and Enterprise Scale need a private email domain; Airtable says addresses such as Gmail or Yahoo are ineligible when upgrading. If your team uses free email accounts, sort out a company domain before planning around Business-only features like field visibility rules or user groups.

Further reads

Sources: Airtable help pages on the permissions overview, base permissions, workspace permissions, Interface Designer permissions, field and table editing permissions, workspace sharing restrictions, billable collaborators, plans overview and using Airtable AI in fields; Airtable pricing page. All checked 17 Nov 2026.

Want a second pair of eyes on your setup?

Bring the process you're trying to fix. On a 1:1 call we'll work out which AI tools should handle it, which parts stay manual, and how to roll it out without disrupting the team.

Book a 1:1 call with me