This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Again running into issues with not having more granular control of User Permissions. Wondering if this is on the Roadmap and if so (Though I know you canโt say when) is it one of the higher priority items?
Thanks Peter. Reading through the whole thread above the focus has been mainly on accidental deletion or seeing figures and general info that isnโt relevant. We would have significant personal and in the UK specifically GDPR issues (affects personal data) without the ability to lock down views. I suspect many potential UK users will not be able to proceed without more granular permissions. Your solutions would appear to solve these for us.
All we really need is another switch on the Duplicate Base options to set a โDo not allow Editors to duplicate this baseโ - keeping this permission at a Creator / Owner level.
What industry do you work in? What role do you have? How are you using Airtable?
We are a business which has developed a business change and planning methodology. Iโm the COO, and have translated our methodology from a spreadsheet based approach to use Airtable.
For data privacy and segregation, we set-up a new base for each project/client and provide the Practitioner / PM editor access to this base. They use this to manage their project, and may give clients viewer or editor access to the base.
Are you most concerned with view access, write access, share access, or another form of information access?
Our #1 concern is being able to stop the duplication of a base. This is for 2 reasons:
a) The base is the codification of our IP - we want to control how this is spread and stop it being copied without permission.
b) We want to give our practitioners control over how clients access the project data.
We are essentially using Airtable as the MVP of our toolset before developing a stand-alone app.
Who are you using Airtable with? With other Airtable collaborators? If so, are these other collaborators base or workspace collaborators? Or, are you using Airtable with non-Airtable users? If so, are they using forms? How are they using these forms?
All collaborators are Base collaborators.
Practitioners are typically Editors
Clients typically engage via forms and read only Table View links
One client role may be given editor access to the base - this is case-by case.
What is the nature of the information that youโre concerned about? Where does it live? In specific cells? In records? In fields? In field configurations? Just in specific views? In entire tables? In the names of records, fields, or tables? In share links?
We are concerned primarily about the protection of the base as a whole rather than individual data elements.
While some degree of role-based permission / data segregation would be useful, this is not critical for us at this stage of development.
Do you use linked records at all? If so, how would you expect that linked records would interact with more granular permissions?
Yes, but as we are not concerned with role based data access, this is not a concern for us.
Can we PLEASE have it so we can turn off base cloning ability?!
Protecting sensitive client information / formulas is a big deal for us. All it would take is hiding a single button for anyone that is not an admin :slightly_smiling_face:
If you want to allow someone to edit only certain fields, weโve created a tool that allows you to do that. It generates a basic editor thatโs ideal for giving access to users who just need to do light work.
Hi there!
We, at Bevouac, are huge fans of Airtable. It (almost) suits our needs perfectly!
The one feature that would make us use only Airtable and not โhome-made codeโ or other tools would be the possibility to share only a portion of the base (one table and selected views i.e.) to an external user and give that person the ability to edit or add records.
I agree, and I believe this needs to be addressed by someone intimate with the security architecture. And I suspect - with these soon to be available features - there may be clever ways to address this requirement.
But, based on this beta, it seems the team is on the right compass heading.
We have been using the beta and it is terrific - solves a lot of problems re: user permissions. However, I donโt believe it addresses the ability to only allow users to see selected information. Hopefully that is the next step for Airtableโs development team as it would be very valuable.
