![]() With Stacker, you can accommodate this use case by creating two different User Roles: one for the job applicants and one for the managers. Additionally, hiring managers should have permissions that let them see all job candidates’ data and update the status of their applications. In that case, candidates should have access only to the data that pertains to them - their name, email address, the status of their application, etc. ![]() This is a really quick thing to do, as you only have to create a Stacker account and enter your Airtable API key.Įach role’s permissions (which we’ll set in the next section) determine what data a specific user can access and how they can interact with it.įor example, say you’re building a job application portal where candidates can enter their information and track the status of their applications. The first step is to sign up for Stacker and connect to your Airtable data. How to Set Highly Granular Permissions for Your Airtable Data Note: Start a free 30-day Stacker trial here, so you can follow along and set advanced permissions for your Airtable data today. We’ll also go over three real-life examples of how Stacker’s permission settings helped our clients build apps on top of their Airtable data, like client portals, internal tools, and more. 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. If I use the “Update Airtable Record” action instead, then I need to insert a sear ch step for the record I want, which I cannot do on a free plan.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. The reason I cannot use Surname & Firstname combo in the Lookup fields is that these values may change and I would end up creating a new record when I actually want to just update the existing record using the record_id. Since I need to lookup the record with unique value, the only way to source that unique value is using some function or formula field within Airtable. However, “phone number” formatted fields are also missing. It seems only text fields are displayed here. The fields that are available are as follows: In fact, very few fields of the Airtable base table are available to select as a lookup field or even a secondary lookup. However, in the Action Step of the zap, when I try to use the “Zapier Key” field as the Lookup Field for my Airtable record, it is not available in the list of fields. Since I am on a free plan, I cannot do a 2-step zap, so I have to use “Create or Update an Airtable Record” to achieve this in one step. When a Zapier table record is updated, I want to update the same record in Airtable. I also have a Zapier table that reflects as subset of these Airtable fields - including the Record_ID The field list is displayed here and the Record_Id field is named “Zapier Key”: This is the unique field for all records in the table. ![]() I have an Airtable base / table with many fields, name address phone etc, and it includes a formula field which is populated with the Airtable RECORD_ID() function.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |