Script / Automation Permissions

[Michael_Andrew]

I am wondering how permissions work with scripts and automations. I have gotten errors in my automations, that the script won’t run because of insufficient permissions. I assume it is because I had set table or field permissions about who can edit them. I assumed that automations could run under any permissions, but it’s clear it cannot. Does anyone know what must the permissions be at table and field level for automations to work correctly?

[Jeremy_Oglesby]

Presumably “Editor” or higher.

[Michael_Andrew]

But now to be able to run any automations, we can’t add table or field permissions that will protect that data. I think this may be suggested elsewhere, but we should be able to select if permissions are overridden by script (like we have for forms).

Field Permissions: No edit privileges except for Scripts/Blocks Product Suggestions

Certain blocks require users add an editable (non-formula) field to a table to hold misc data which shouldn’t be directly edited by the user (i.e. the Map Block requires a geocache field). Many Script Block scripts semi-automate or standardize data entry processes to provide a form of data validation or workflow integrity. I think it would be nice if Airtable’s field permissions included a toggle for " Allow this field to be set in scripts/blocks/API" when the field permissions are set to: “Who…