- Airtable portals let people outside your organisation log in, see only the work that’s theirs, and edit it. Nobody needs a paid seat, and nothing has to be exported and emailed around.
- The part most teams miss: you don’t build a second solution for them. A portal layers onto an interface you already run.
- Most of the work sits in your permissions architecture, which comes down to a people table, a linked record and one filter set to the current user. Once that’s in place, the sharing part takes about five minutes.
- Guests can’t share your interface, see your other workspaces, or reach Airtable’s home screen, and those limits are deliberate rather than gaps in the product.
Prefer to watch? The full session recording is on Airtable’s site, or read on for the write-up.
Nifty co-founder Nathan Coffey ran a live build for the Airtable Media & Entertainment User Group on Airtable portals for external users.
He took a creative operations interface a team already used every day and opened it up to outside contractors, live, in about five minutes.
Here’s the business case, the build, and the limitations worth knowing first.
Where external collaboration breaks
Almost no media team delivers work on its own. Campaigns often pull in freelancers, production crews, creative agencies, media buyers and partners. Your plan lives in Airtable, and theirs tends to arrive as an email attachment.
So you export a view to a spreadsheet, send it out, and spend the next week working out which version is current. Or you buy a seat for someone who needs one screen for six weeks. Or you share a read-only link and accept that they can’t update anything, which puts you back to updating it on their behalf.
The cost isn’t only the admin. Once data leaves the base, you’ve lost track of where it sits and who holds a copy. That’s how one source of truth quietly turns back into a pile of spreadsheets labelled v1, v2 and v2_final.
What shifts for you
Your partners work on the live record
Sharing used to mean exporting. Now the freelancer, the agency or the media buyer signs into your base and works on the live record. Nothing gets emailed out, so nothing drifts out of date, and your data stays where you can see it. This is the gap portals were built for: external people who need to edit and collaborate, not only read.
You can bring in a freelancer today, without an IT conversation
Onboarding was always the real blocker here. Your freelancer had to create an Airtable account before they could open anything, which often meant raising a ticket with their own IT team first. With a portal they land on a sign-in page you’ve customised with your logo and background, and they’re in.
Edit rights without handing over your base
You used to choose between a read-only view and a full paid seat. Now you pick the level: commenter, read only, or editor. An editor works the way your internal team does, commenting on records and moving work through your statuses. What they can’t do is share your interface, browse your other workspaces, or navigate to Airtable’s home screen. They’re in your portal, or they’re out.
No second build
Opening a workflow to outsiders doesn’t mean designing a separate Airtable solution for them, or rebuilding the base you have. It layers onto the interface you already run. If you haven’t built one of those yet, start with custom Airtable interfaces for campaign management. As Nathan put it on the day, this doesn’t have to be a bill you pay a consultant for. If your Airtable is in reasonable shape, it’s a job you can do yourself.
How to set up an Airtable portal, step by step
Prefer to watch Nathan build it live? The full session is embedded below, or read on for the steps.
Heads up: the names and numbers in the demo are a worked example, not a real team.
The first step in adding an Airtable portal to your base, is settling your permissions architecture, because that’s what decides whether any of this works. Nathan built on a creative operations base: campaigns, creative requests raised against those campaigns, and a delivery hub showing each person what’s on their plate.
Part one: set up your permissions architecture
- Build a people table. One record for every person who will touch the system, internal and external, with name, email and team. Nifty recommends this as one of the first things to build in any base, because it’s what lets you tell which group someone belongs to and what they should see. It’s the same foundation an Airtable resourcing base is built on, so if you already have one, you’re a step ahead.
- Add your external partners before you invite anyone. You can stage a hundred contractors in the people table, tag them to the right teams, and send invites later. Curate the list first, invite in bulk second.
- Link your work to the people table. On your requests, tasks or assets table, make the owner field a linked record pointing at people, not a plain collaborator field, because the collaborator field won’t reliably hold someone from outside your organisation.
- Look up each owner’s email onto the work table. This is the field your filter reads, so it has to sit on the same table as the work.
- Filter the interface by the current user. In the interface filter configuration, add a condition where that email field contains the current user. Publish, then preview as one of your people to check they see only their own records.
- For agency-wide access, filter on a team instead. Add a team table. Put a lookup on the people table that pulls in every email on a team, then look that field up onto your work table and name it clearly, for example “all access emails”. Filter on that, and the whole agency sees the agency’s work rather than one person’s slice of it.
Part two: share it as a portal
With the architecture in place, this is the five minute part.
- Share the interface, then choose “Invite guests”. Open the interface, hit “Share”, and look for the “Invite guests” toggle, which is easy to walk past. Take care not to use “Invite collaborator” instead, because that adds someone as a paid seat on your account as though they work for you.
- Toggle portals on in the admin panel if prompted. The first time you use portals, Airtable flags that they bill differently to your plan and links you through to the admin panel. On a Teams plan you may need your workspace owner to switch it on for you. On enterprise, that’s a job for your Airtable admin.
- Customise the guest sign-in page. The option sits in the same “Share” panel as the invite controls, as a link to the customised guest sign-in page, so it’s easy to miss on your way to sending the invite. Add your logo and a background image. This is the first screen a guest sees, and it’s what makes the experience feel like yours rather than Airtable’s. Customisation depends on your plan, so check Airtable’s portals documentation if you can’t see the option.
- Or create a scoped invite link. Instead of naming individuals, create a link and restrict it by domain. You can list several agency domains, comma separated, or allow any email address. Keep guest links separate from the ones you send internally.
Your guests can read your internal comments. Worth checking before you share anything. Airtable has a setting called “Prevent external users from seeing each other”, and it’s always in effect for portal guests whether you toggle it on or not. It redacts names, so comment authors and mentions show as “Unknown” to an external guest. What it doesn’t do is hide what the comment actually says. So if your team talks internally in comments on records a guest can see, the guest can read every word of it. If that content has to stay internal, turn comments off in the record detail layout settings.
One portal per base. You can share several interfaces inside one portal, as long as they live in the same application. A portal can’t span multiple bases, so multiple bases = multiple portals.
Guest links and internal links aren’t interchangeable. If someone on your own company domain signs in through the guest link, Airtable attributes them as a regular user and bills them as part of your organisation. Portals aren’t a way around paying for seats.
A guest invited to a second application becomes a paid seat. Guest status only covers someone interacting externally with one application. If an agency works across several of your Airtable apps, they’re upgraded automatically. Worth planning for if you expect cross-functional external collaboration.
Nothing in the share menu says “portal”. There’s no button labelled “Invite to a portal”, so it’s easy to share the wrong way by accident. Nathan’s advice: name one person as the admin who owns the people table and the permissioning. That’s how you avoid an unexpected bill from Airtable.
Use the email filter, not the collaborator field. Airtable’s collaborator field gets unreliable as soon as you try to put an external person in it. Email holds up better, and it lets you build your list before anyone has been invited to the base at all.
Naming conventions matter more than you expect. Once a personal email field and a team email field are both feeding the same filter, picking the right one gets confusing fast, which we encountered live in our demo. Name the fields so the filter is obvious.
FAQ from the session
Do you have to add specific people as guests, or can you share one link that anyone who signs in can use?
Both work. You can invite named guests, or create an invite link. The link can be restricted to specific domains, comma separated if you work with a few different agencies, or opened up to any email address. Just keep guest links separate from your internal ones.
What can a portal guest do, compared to a full team member?
It depends on the access level you grant: commenter, read only, or editor. As an editor they work in the base much as your own team does, commenting on records, moving work through your statuses and editing anything you’ve exposed, using any view type or interface feature within their access. What they can’t do is share the interface, see your other workspaces, or navigate to Airtable’s home screen. If they already have an Airtable account, your portal appears on their home screen alongside their own.
Apart from the email filter, how else can you limit a guest to records that apply to them?
Team-based access. Build a team table, look up every team member’s email onto your work table, and filter on that field instead of the individual’s email. The whole agency then sees the agency’s work. Airtable’s user token is another route, but for portals the email approach is more reliable, because the collaborator field struggles with external people.
Do you get notified when a portal user changes something?
Not by default. There’s no single switch for “tell me everything portal users change”. You set up notifications and automations for guests the same way you would for internal users, and you can use the people table to tag someone as external so you’re alerted when they move a status or mark something delivered. It works, but you have to build it deliberately.
Try it yourself
Recording Watch the full session — one line on what it is
AIRTABLE DOCUMENTATION Airtable’s portals documentation for plan requirements, the admin panel toggle and current pricing
AIRTABLE DOCUMENTATION Managing and sharing Airtable interfaces for the collaborator visibility settings covered in the gotchas above
Nathan Coffey is a co-founder at Nifty and leads the Airtable Media & Entertainment User Group. He found Airtable in 2018, back when the product was, in his words, “literally just a database.” He spent the years after that consulting at Airtable, delivering a couple of hundred builds, almost all of them in media. He now does that work as an external partner, building on Airtable and standing up the internal teams who run it across large, cross-functional organisations. Connect with him on LinkedIn.
Nifty is the Airtable transformation partner for media companies. Not just a build team. We’re a Gold-certified Airtable partner, top-rated globally, trusted by Netflix, Disney, CBS, Paramount and Yahoo. We take teams from first build through to adoption and long-term ownership, so what you build gets adopted, not shelved.
What's next
If this was useful, there’s more where it came from:
- Follow Nifty on LinkedIn for ongoing Airtable tips and builds
- Join the Airtable Media & Entertainment User Group to catch the next live session
- Talk to Nifty if you want help opening your own base up to the people outside it
