Specifically, you’ll learn how to set granular permissions for who can see and edit your Airtable data at the table, record, or field level. In this article, we’ll show you how you can overcome this issue with Stacker - our tool that helps businesses who have data in Airtable (or other platforms) customize how that data is presented and set advanced permissions for users to interact with that data. Besides being more time-consuming and tedious, this workaround can be used only to add new records or fields, not to edit existing ones. You can create a view link and a form, where the link shows people only certain records or fields, while the form lets them add new ones.If you need people with the link to be able to edit something in your base, this method won’t work. However, these links are read-only, meaning you can’t share editable views. You can create a view inside a base and send a view share link that provides access only to that view and no other records.Outside of creating new bases for each different collaborator, there are two workarounds to this issue, but they have significant downsides: Collaborators can always access the entire base they’re invited to, which is a problem if you don’t want them to see the data in a specific table, record, or field. As a result, there’s no way to share only a portion of your base (like a single table) with collaborators. While useful, these collaborators can only be added at the workspace or base level. For example, editors can do things like add, modify, and delete records, while commenters can only comment on records. Airtable lets you add four types of workspace collaborators to a base:Įach type of collaborator has different permission levels, which allow or prevent them from taking certain actions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |