Adding a client portal to an Airtable base usually means one of two things: paying for more Airtable seats, or building a full Softr or Noloco app. Both have overhead — cost, complexity, or both.
At GAP Consulting, we've found a third option for lightweight use cases: mini-portals built with Fillout and Airtable. No new seats. No separate app platform. Just a form with authentication that reads from and writes to Airtable.
Here's how we build them.
Try Fillout free and start building authenticated portals with your Airtable data.
Disclosure: some links in this post are affiliate links. If you sign up through them, GAP Consulting earns a small commission at no extra cost to you.
A mini-portal is a focused, login-protected view of Airtable data — not a full application, but more than a shared view. It lets a specific user log in, see only their data, and take a limited set of actions (like updating a status or submitting a form).
The key constraint: the user doesn't need an Airtable account. They authenticate through Fillout using their email or Google login. Fillout handles the auth, then looks up the user in your Airtable Users table to determine what data to surface.
This pattern works well for:
The base needs a Users table. At minimum, this table holds the user's email address and links to whatever records they should be able to access — tasks, projects, invoices, or whatever your use case requires.
Each user record is linked to the relevant data records. When a user logs in through Fillout, the form looks up their email in the Users table, finds the linked records, and displays only those.
The record ID of each linked item becomes the key that connects the Fillout form experience to the correct Airtable records.
In Fillout, you start a new form and enable user authentication — email/password or Google OAuth. Once authentication is set up, the form can access the respondent email variable, which is the logged-in user's email address.
Use that email to look up the user record in Airtable. From there, Fillout can pull in linked task or project records and display them as a dynamic list. The user only sees their own data.
One important detail: some fields in your Airtable records are for internal use only and shouldn't be writable through the portal. Fillout's no-action conditions let you display a field as read-only or skip it entirely based on the respondent's context.
This gives you control over what clients can see vs. change — without building a separate permission system.
When a user submits the Fillout form, you often want that action to trigger something in Airtable: updating a status field, adding a timestamp, notifying a team member. Fillout supports webhook submissions, which means every form completion can trigger an Airtable automation.
The automation receives the webhook payload, finds the right record, and updates it accordingly. This keeps your Airtable data in sync with client actions in the portal, without requiring manual review.
Mini-portals aren't the right tool for every use case. If you need complex navigation, multi-table views, or a polished branded experience, a proper portal platform is worth the investment.
But for lightweight, focused workflows — a client checking their project status, a vendor uploading a deliverable, a contractor confirming a task is done — this pattern is fast to build and easy to maintain.
Get started with Fillout and build your first authenticated mini-portal in under an hour.