Skip to main content

Who can use automations

Find out who can create, edit, run, and see automations, and which person an automation acts as when it changes records, sends emails, or adds comments.

Written by Leo

Permissions decide which people can build and manage automations, and which person an automation acts as when it runs (the person is called the author). They're meant to help you keep control over what automations change in your workspace.

You can use this page for many things, including:

  • Deciding who on your team may build automations.

  • Finding out why an action fails with a permission error.

Opening the ••• menu of the Update the current record action and selecting Author, which lists Automation under General, the workspace members under Members, and the person fields of the expense such as Submitted by and Approver

Who can use automations?

  • Automations are available on the Free, Plus, and Premium plans. The number of automation actions per month depends on your plan. See the limits for your plan on our pricing page.

  • Workspace admins can create, edit, pause, and delete automations.

  • Other members can't see automations or their runs.

  • To open the Automation Center from the sidebar, you need to be an Organization admin or Organization owner and a Workspace admin in at least one workspace. Everyone else doesn't see Automations in the sidebar. Learn more about organization roles →

  • The Automation Center shows only the workspaces where you're a workspace admin, and only database apps you have full access to.

Create and edit automations

To create an automation, open a database app and click the automations icon at the top right (Create and view automations), then New automation. People who aren't workspace admins don't see the automations icon at the top of the database or Automations in the app menu. No message appears. The Automation Center in the sidebar is only for organization owners and admins who are also a workspace admin.

Automations you create in the editor are Active right away. To stop one, select its status. It switches to Paused. Then select Save changes.

Run an automation

An automation runs when its trigger fires. You can also start it yourself with Manual run. Workspace admins can start a manual run. The changes of the run are attributed according to the Author setting of each action, not to the person who started the run.

The author of an action

Actions that change data, such as Update record, Create record, and Add comment, have an Author setting in the action menu. It decides which person Tape shows as the author of the change, for example in the activity of a record. Author lets you choose the automation itself, a member of the workspace, or a person from a field of the record. Without a choice, the change is attributed to the automation.

If you choose a person under Author, Tape checks that person's permissions when the action runs:

  • For Create record, the person needs permission to create records in the database.

  • For Update record, the person needs permission to edit the record.

  • For Add comment, the person needs permission to comment on the record.

  • Delete record and Restore record don't check the author's permissions.

If the person is missing that permission, the action fails.

Permission errors

  • An action fails with a permission error. The step fails with a message like Actor of type USER with id 123 has invalid permission to access record 456. USER means the person under Author lacks the right. If it says WORKFLOW_DEF, the automation itself has no access to the record.

  • A person can't see the Automations area. They need to be an admin of the workspace and have full access to the database app.

  • A person can't edit an automation. They need to be an admin of the workspace.

Learn more

FAQs

Do I need an admin to build an automation?

Yes. Only workspace admins can create and edit automations.

Can guests use automations?

No, guests can't see or edit automations, because only workspace admins can, and guests can't be workspace members. A change a guest makes can still start an automation if it matches the trigger.

Can an automation change a record that I can't edit?

Yes. An automation has its own access to the workspace, so it can change records that the person who triggered it can't edit. If you set a person under Author, that person also needs the right to make the change, otherwise the step fails.

Still have questions? Find answers and get help from community experts in the Tape community →

Did this answer your question?