Softr Docs
Search…
Edit Permission
Configuring permissions for editing Airtable data
Here, you can define permissions to specify which bases, tables, fields, and records from your Airtable account the users can edit. After defining the permissions here, you can enable editing on any List, List Details, or Table block, so that users can edit the data that appears on the block, thus updating it in your Airtable base. We'll discuss that further in this article. Now, let's see how you can add and configure permission rules.
The Edit Permissions feature is available only for Softr's Professional and Business plan customers.
Below is the list of fields that are supported or not supported for editing.

Supported

  • Checkbox
  • Single Select
  • Rich Text
  • Date
  • DateTime
  • Single Line Text
  • Long Text
  • Single Select
  • Multiple Select
  • Email
  • URL (validation to be added)
  • Currency (validation to be added)
  • Number (validation to be added)
  • Percent (validation to be added)
  • Phone Number (validation to be added)
  • Multiple Attachments (coming soon)
  • Multiple Linked Records (coming soon)
  • Rating (coming soon)
  • Duration (coming soon)

Not Supported

  • Single Collaborator
  • Auto Number
  • Barcode
  • Button
  • Count
  • Created By
  • Created Time
  • Formula
  • Rollup
  • Last Modified By
  • Last Modified Time
  • Multiple Collaborators
  • Multiple Lookup Values

Adding a Permission Rule

Let's go through the steps of adding and configuring a permissions rule. To create a new permission rule, you need to click the Add edit permission button.
Add edit permission
In the pop-up that appears next, you need to add a name for the rule and select to which user group it should apply.
Configuring the permission rule
Adding custom user groups to the permission rule is available only for Business plan customers. For the Professional plan subscribers, only the "Logged in users" option will be available, and they can add just one Permission rule.
If there are multiple permissions set for a particular table (e.g. you have more than one permission rule that refer to that table), they will be combined together. If the permission rules are conflicting, the one that provides the user with a larger set of editing capabilities will be given a priority.

Configuring Record- and Field-Level Permissions

Next, you need to add all the bases and tables for which you want to specify the permissions. For each table, All Fields and All Records will be enabled by default. If you want to set more specific rules, you can turn the toggles off and configure each field separately, so that users are able to edit only the selected fields.
For Record-Level Permissions, you should define a condition, so that the given user is able to edit only those records that meet the condition. This works similar to List Conditional Filtering explained here. In the example provided for the conditional filters, the users can only see the tasks that are assigned to them (contain their email address). If you set a similar rule for the record-level permissions, the users will only be able to edit the tasks that are assigned to them. We'll discuss this example in greater detail below.
Configuring the permission rule
After defining the permissions for all the necessary bases/tables, just hit Create permission, and the permission rule will be saved in the permissions list.
As soon as you've configured your permission rule, you can navigate to a specific List, List Details, or Table block to enable editing. See how that's done here.
Last modified 1mo ago