These are Airtable error messages that indicate that the permissions must be verified. If the extension stops working suddenly and you see an error message related to permissions or authorization, you can troubleshoot the problem by going through the possible reasons in this article.
Common error messages |
|
|
|
|
First steps
Before proceeding, make sure that you are logged in with Airtable using the account that is integrated with miniExtensions. Check this article on how to identify the account. Once you know the account, identify the role it has in the workspace:
Log in to Airtable with the account connected to miniExtensions and go to the workspaces where the tables you use reside. You'll see the role of your Airtable account in the right panel of the workspace:
Possible causes
1. No permission or read-only access in Airtable
Depending on how the permissions are configured in Airtable or how the base was shared with you, the account you use with miniExtensions could have restrictions at different levels. If you can't edit a record or field on Airtable, you won't be able to edit it on miniExtensions:
Base level: Your Airtable account may have read-only access to the base. You'll need to have the owner, creator or editor role; if the role of the account in the workspace is read-only or commenter you need to ask a higher role to upgrade it.
Table level permissions. Verify that the tables your extensions use have edit permissions for the role of the connected account. Check this in the Edit table permissions option:
Field level. Some fields have restricted permissions. If you receive an error message when trying to edit a specific field, check the field configuration in Airtable through the Manage fields option.
💡Tip: This might be the reason you encounter the error randomly/intermittently in the same form or child form. You have to find the field that has this restriction and adjust it accordingly.
2. Base missing from the Airtable integration
Make sure that the Airtable integration includes the base that you are trying to access. You can learn how to update your Airtable integration in this article.
3. Invalid Personal Access Token
Our current site (web.miniextensions.com) does not use an API key or Personal Access Token at all since the connection is established in an entirely different manner (OAuth).
Users of our legacy site (app.miniextensions.com) need to switch to the Personal Access Token (PAT) system as explained in this article.
The user may have lost access. If the Airtable user that set up miniExtensions doesn't have access to the base anymore, the Airtable PAT that was used to connect Airtable with miniExtensions will not be valid anymore. Therefore the connection between the two will become invalidated (unauthorized).
4. Synced Table
You’re trying to set up the extension on a Synced table to edit (read-only) fields.