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?
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.
Hey guys, i had the same issue so we built a way to sync base together so we can share a portion of base with edit access to our clients.
We are thinking of sharing it, if you are interested click here
For sensitive, critical data, if I want to get someone to help with data entry, I need to be able to give them permission to add records but not to delete anything. I want to be able to have someone create records without being able to accidentally delete or otherwise modify the base/tables.
Editor level permissions minus “delete” would accomplish this.
A write-only permission level would be great too - if I only need them to enter new data, but don’t want them to modify existing data, this would be the better implementation.
Doesn’t this support already exists through the forms system? I’m not a security expert, but I think a form abstracts data producers away from your base.
Hi, just following up about syncing part of your airtable base with clients and partners.
We released the beta version, you can signup there : https://trybases.com
Check out this service. https://strictapi.com Looks like they just lunched. They act as proxy between Airtable API and the client. They will create 2 API users for you and each user can have access to different tables.
Can’t believe Airtable can add table and field level permissions, but still allows any user with edit rights (i.e. team member) to see ALL DATA in ALL TABLES. Still makes it useless for me to add team members so must rely on other tools almost solely because of the VIEW ALL strategy employed. Sharing a read-only view in some way does not help.
BTW the simple solution seems to make editable Views sharable to Users and/or Roles. If a field isn’t in the view then the shared user can’t edit. If a Table has no shared views then it is private by nature. Simple, and much needed.
The best way that we have of accomplishing this right now is Stacker. It’s actually pretty amazing what they’ve accomplished, because it’s both powerful AND easy to setup. Would be awesome if Airtable bought them and integrated it into the product.
