How Do You Give Clients Access To Only Their Airtable Records

Last updated: 21 August 2026.

You've got one Airtable base holding every job, case, or account. A client logs in to check on their own, and for a second you're not sure: can they see anyone else's information too?

Airtable has a native way to show each logged-in user only the records assigned to them. It uses a user field and a current user filter.

Here is exactly how to set it up, what it does, and what to watch out for when you have multiple clients using the same interface.

TL;DR

• Airtable's native way to do this is a filter tied to a user field and Current user, not a plain email field.
• It works for logged-in users. It does not work for anonymous visitors using a public interface link.
• You need to set the filter at the interface-page level, so each page that needs this restriction needs to be configured correctly.
• Airtable also lets you control which fields users see in interface record details, so record filtering and field visibility are separate things to check.
• Always test the interface as an actual client or test user before sharing it.

What do you need in place before you can filter records by client?

Before the filter can work, Airtable needs to know who the person viewing the interface is.

That means the client needs to access the interface as a logged-in Airtable user rather than through an anonymous public link.

You also need a user field on the table you want to filter. This is a specific Airtable field type that stores an actual Airtable user, rather than a text field containing someone's email address.

For example, you might have a Client user field in your Projects table. Each project is assigned to the client who should be able to see it.

Once that is in place, Airtable can compare the logged-in user with the user stored on each record.

How do you set up a filter so each client only sees their own records?

There are two ways to configure this, depending on whether you want to filter an entire interface page or a specific element.

Option A: Filter an entire interface page

1. Open your base and click into Interfaces.
2. Open the page you want to restrict.
3. Click near the page title to open the page properties.
4. Under Data, find Filter by and click the cogwheel icon.
5. Select + Add condition.
6. Under Where, choose your user field.
7. Set the user to Current user.
8. Publish the interface.

Airtable will then show each logged-in user the records where they are included in that user field.

Option B: Filter a record list element

If you only want to apply the rule to a particular list or grid:

1. Select the record list element on the page.
2. Open its settings in the sidebar.
3. Set the element to Viewer's records.

This uses the same basic idea: Airtable matches the logged-in user against a user field on the record.

You don't need to create a separate interface for every client.

What plan do you need, and who can turn this on?

The Current user / Viewer's records functionality is part of Airtable's Interface Designer. Airtable's current documentation lists Interface Designer across all plan types, although sharing an interface separately from the underlying base is restricted to paid plans.

You'll also need the appropriate Owner or Creator permissions to configure the interface. Airtable recommends that creators use Preview or View as to test what other users can see before sharing an interface.

On Business and Enterprise Scale plans, Airtable also supports user groups, which can be useful when the same records need to be visible to several people rather than one specific user.

Does this work with a public link, or only with a logged-in user?

The Current user filter depends on Airtable knowing who is viewing the interface.

A public interface link does not give Airtable a logged-in user to match against, so Current user filtering isn't supported for publicly shared interface pages. Airtable specifically warns that publicly shared interfaces can potentially expose data when this type of filtering is involved.

So if you need Client A to see Client A's records and Client B to see Client B's records, use authenticated access rather than a public link.

What does the filter actually do?

The filter controls which records are shown to the logged-in user on that interface page.

For example:

Airtable's interface permissions also let creators control which fields appear in record details, so don't treat the record filter as the only access setting you need to check.

For a broader explanation of Airtable's permissions and where they become difficult to manage, see our guide to Airtable permissions: what they can and can't do.

How do you test that the filter is actually working?

Don't just trust the filter panel.

Test the interface as an actual client or test user.

Airtable itself recommends using Preview or View as to check the sharing flow before giving users access.

Check three things:

1. The client only sees the records assigned to them.
2. They see the fields you actually want them to see.
3. The same access rules work on every page they can reach.

That last point matters because Current user filtering is configured at the interface-page level. Setting it up correctly on one page does not automatically configure every other page in your interface.

What happens if a client is assigned to multiple records?

That's exactly what this setup is designed for.

If the same client is assigned to 20 projects in your user field, the Current user filter can show that client all 20 projects.

You can also use different filter operators when a user field contains multiple users. For example, Airtable supports conditions such as is any of or has any of, depending on how the user field is configured.

Be careful with broader matching rules, though. If several users are assigned to the same record, more than one person may be able to see it.

Test those cases before giving clients access.

When does this become difficult to manage?

Current user filtering can be a simple way to give clients access to their own records.

The challenge is that you need to keep the access rules correct as the interface grows.

Imagine you start with:

• 10 clients
• One project page
• One user field

Then your operation grows and you add:

• A project dashboard
• A document page
• A requests page
• An invoices page
• Contractor access
• Internal team pages

Now there are more pages, more user types, and more rules to check.

The problem isn't that Airtable can't filter the records. It's that external access has become a bigger part of the workflow.

That's where teams can start looking beyond a filtered interface.

If you want to understand the separate problem of duplicating interfaces for different clients, see How to stop duplicating the same Airtable interface for every client.

What if clients need to do more than view their records?

Sometimes the requirement starts simply "I want each client to see their own projects." Then it grows into "I also want them to submit requests, upload documents, see project updates, and work with our team."

At that point, you're no longer just filtering an Airtable interface. You're managing what different people outside your company can see and do.

For example, a client might need to see their projects, submit a request, upload documents, and track progress. A contractor might need to update only the jobs assigned to them. Your internal team needs access to everything.

You can keep adding filters and access rules inside Airtable as these needs grow. Or you can keep Airtable as the place where your data lives and give each external user a dedicated portal to work from.

With Noloco, you can build a client portal on top of your Airtable data, so each client sees the records, pages, and actions relevant to them. Instead of sharing your internal Airtable setup with external users, you give them a place designed around what they actually need to do.

This can be useful when clients need to:

• See only their projects, jobs, or accounts
• Submit requests or update information
• Upload and access documents
• Track progress without asking your team for updates
• Work across several parts of a process in one place

Your team can continue using Airtable behind the scenes while clients, partners, or contractors get their own experience on top of the same data.

Final thoughts

Airtable can genuinely show each logged-in client only their own records: add a user field, assign each record to the right user, and filter the interface by Current user.

It's useful for simple client-facing setups, and you don't need to duplicate an interface for every client.

Just remember that the filter is configured per interface page, and it doesn't apply to anonymous public links. Test the experience as an actual client before sharing it.

If clients eventually need to do more than view their records (submit requests, upload documents, track work, or interact with your team), you may outgrow a filtered interface and need a dedicated client portal instead.

Frequently asked questions

Do I need a paid Airtable plan to filter records by client?

The Current user / Viewer's records functionality is available in Airtable's Interface Designer. Sharing an interface separately from the underlying base is a paid-plan feature.

Can I use an email field instead of a user field?

No. The Current user filter requires an Airtable user field, which stores an actual Airtable user rather than a plain text or email field.

Does the Viewer’s records filter work on a publicly shared link?

No. Current user filtering depends on a logged-in user and isn't supported on publicly shared interface pages.

Can a client see records I didn't mean to show them?

They can if the interface is configured incorrectly or another page doesn't have the appropriate filter. Test the interface using the same access your clients will have before sharing it.

Can I give several clients access to the same record?

Yes. Airtable supports user fields containing multiple users, and the available filter operators can determine how those users are matched. Test the setup carefully if several users should share access to the same records.

When do you need more than Airtable's current-user filtering?

Current-user filtering works well when the main goal is to show each logged-in user their own records. If external users also need to submit requests, upload documents, track work, or access different parts of your process, you may need a more complete client-facing setup. In that case, you can keep Airtable as your data source and use a portal tool such as Noloco to give clients and partners their own place to work.

Related resources

• Airtable permissions: what they can and can't do
• How to stop duplicating the same Airtable interface for every client
• Noloco vs Airtable Interfaces
• How to build a portal around your Airtable data