Nope. Airtable was designed to allow for easy collaboration and is based on the idea that all collaborators can be trusted to view all data in the base. This is slowly evolving, but Airtable still should not be used to store private or sensitive information that some collaborators should not have access to.
You bring up some great points. If you grant access to your base that user has access to the base data. Even with permissions they can still download the data. That said you have to be careful about how you store sensitive data.
There are work arounds, like creating a sensitive base that only you can access, and syncing only pertinent records from that base.
Along the same channel of @kuovonne’s response, the weakest part of your data security procedures are you, your team, and your users.
You have to remember that Airtable is first a collaboration platform that happens to be built on the structure of a database.
We all had a slightly similar conversation in this thread, where the sentiment is primarily the same.
I’m going to go on a bit of a brain dump since this has been on my mind lately, but I think it’s contextually applicable to the conversation of data security, and I think that there’s a good chance that people in the future will find these threads with similar concerns.
Thus I think they’re important for thinking about how we as users, consultants/freelancers, admins, and developers can ensure security and how Airtable as a platform and company handles our data.
More importantly, these conversations set a precedent in continuing to push for more powerful tools for managing user permissions and data security
As I’ve spent more time working with data and building solutions for a vast array of teams in unique industries, I’ve spent more and more time thinking about data security.
When working with larger teams and organizations, I now keep a list of things down when I “score” infosec.
Does this industry operate under regulatory compliance standards? A few companies/teams I’ve worked with are subject to:
Does someone have an invite into or access to this base or workspace?
Who is responsible for inviting new users?
Who is responsible for off-boarding users?
Are we auditing user access?
Are there any viewing links? Where are they? What are they for?
Are those viewing links domain or password restricted?
Do they allow for base syncs?
Who has developer & scripting permissions? Why?
Are they getting PRs or code reviews?
What do their scripts or applications do?
What integrations are active? Who owns the API keys?
What data are we syncing out of Airtable into other possibly unsecured systems?
Many of these things aren’t available outside of enterprise accounts, which I view to be a huge failure in supporting small businesses or teams that cannot afford the $36,000 enterprise startup fee but still need to confidently manage access to sensitive d,ata not just defined as PII.
That being said, asking these questions keeps me (and, by extension, those I work with) aware of the potential risks of sending someone what seems like a harmless shared view.
We can often get so caught up in building and pushing the boundaries of what’s possible with platforms like Airtable that we can easily forget how to retain boundaries that keep us, our clients, and our teams safe.