Only organization admins can share automations. Non-admin members cannot share, even if they have the Admin role on a specific automation.
To give a team admin access to all automations in the organization, assign the Automations Admin role to their group instead of sharing automations individually.
| Sharing method | Core | Enterprise |
|---|---|---|
| General Access (everyone in org) | ✅ | ✅ |
| Individual users | — | ✅ |
| Groups | — | ✅ |
Roles
When sharing an automation, you assign a role that controls what the recipient can do:| Role | Permissions |
|---|---|
| Admin | Full control: edit, delete, share, run, and view all executions |
| Executor | Run the automation and view their own executions |
| Viewer | View the automation and execution history (read-only) |
Share with everyone (General Access)
Available on Core and Enterprise plans.
- Open the automation → click Share
- In the General Access section, select Everyone in
Share with individual users
Requires Enterprise plan.
- Open the automation → click Share
- Search for and select users to add
- Choose a role for each user
Share with groups
Requires Enterprise plan. Custom groups must be configured first.
- Open the automation → click Share
- Select groups to add
- Choose a role for the group
Remove access
- Click Share → find user or group → click role dropdown → Remove access
For Automations shared with users
Automations that are shared with a user will appear in their Automations list. Depending on their role, they can run or view them on any project or repository you have access to.
Automations run under your identity - commits and PRs are attributed to your account, using your SCM permissions.