Skip to main content
Question

Best way to restrict who can see sensitive fields in a shared base?

  • Nov 18, 2026 8:06 AM UTC
  • 3 replies
  • 21 views

cyberseal
Forum|alt.badge.img

I am setting up a base to track client project details for a small team. Some fields (like contact details and internal notes) should only be visible to certain collaborators.

What is the recommended way to limit access to specific fields or records? Are interface permissions or filtered views enough, or should I split this into separate bases?

I work at Cyber Seal Infosec Solutions (https://www.thecyberseal.com/), so security of shared data is a priority for us.

https://www.thecyberseal.com/

3 replies

Kitkate
Forum|alt.badge.img
  • New Participant
  • Nov 18, 2026 10:37 AM UTC

Hello!

I'm not an expert in cybersecurity, though I've studied European privacy law since its inception, and one principle has stuck in my mind: systems have to be private and secure by design. I always ask myself what's the most secure/private solution by design within an environment.

In this case, the safest option is to separate the datasets by creating two different bases.
This, for example, is the solution applied within health and finance institutes. You can even see a physical separation in offices for teams dealing with sensitive data :) 

Just be aware, two separate bases don't communicate/sync as easily as two tables within the same base. That's the trade-off to keep data safer. 


WorkflowEngineer
Forum|alt.badge.img+1

Whether those teammates need access to the underlying base determines which approach fits.

Filtered base views don't provide a confidentiality boundary. Field and table editing permissions limit what people can change, not what they can read.

If teammates can work entirely through interfaces, start with interface-only access, which requires a paid plan. Give them a separate interface with only the information they're allowed to see, and don't rely on conditional field hiding for sensitive values. First remove their existing base access and any inherited workspace access. An interface doesn't reduce those permissions.

If they need underlying base access, separate bases are the stronger fit. Put sensitive data in a base they can't access, including through workspace membership. Splitting the bases isn't enough if workspace permissions still give them access to both.

https://support.airtable.com/articles/2193541120-interface-designer-permissions

Do the restricted teammates need the underlying base, or could they work entirely through an interface?

-Roe


StevenMock
Forum|alt.badge.img
  • New Participant
  • Nov 18, 2026 4:04 PM UTC

Same problem here. We track client projects for a small team too, and contact details plus internal notes were exactly the fields we had to keep private. Filtered views were not enough for us: anyone with base access can still reach the hidden fields, so we stopped treating a filtered view as a security boundary.

 

What actually worked was structural. The shared client table holds only what everyone is allowed to see: name, project, status, and one owner attached to the record. The internal notes and every touch get logged in a separate linked table that the shared interface never shows. One record per client, and everything sensitive lives against that record in the private table, not as a field on the shared one.

 

That one rule — every client record has one owner, and every touch logged against the record — is also what kept our follow-up sane once we passed ~200 past clients. Spreadsheets died the day we passed ~50 records, for the same reason: the moment notes and follow-ups live in the wrong place, nobody trusts the record anymore.