Manage automation restrictions
Starting from Jira 11.3.3, you can apply automation restrictions . This feature is disabled by default and will be enabled in Jira 12. To enable it, turn on the a4j.automation.component.restrictions feature flag.
Automation restrictions let you control who can create, edit, enable, or disable automation rules that use specific components. This is useful when project admins are allowed to manage project rules.
With automation restrictions, you can:
- allow only specific groups to create rules that use restricted components
- limit editing, enabling, or disabling rules with restricted components to allowed groups
- prevent project admins from managing rules with restricted components unless they belong to an allowed group
Before you begin
- Automation restrictions don’t affect admins with global permissions. These admins always have full access to all automation rules.
- Check if the Allow project administrators to manage project rules checkbox is selected. If project admins aren’t allowed to manage project rules, only global admins can manage automation, so you don’t need to restrict components. How to manage permissions for project admins
- You can configure restrictions for a specific component if a user isn’t part of any allowed group for that component.
- You can’t restrict copying, deleting, importing, or exporting rules, but users won’t be able to publish rules with restricted components.
- Imported rules with restricted components are disabled by default and can’t be enabled.
Adding automation restrictions
To add automation restrictions:
- Go to Settings
, then select System.
- From the sidebar menu, select Automation restrictions.
- Select Add restrictions.
- Choose one or more user groups that should have access to the restricted automations.
- Select the components you want to restrict for the chosen groups.
- Select Save.
The new restriction appears in the list. Only users in the selected groups can use the restricted components. Users will see a RESTRICTED label next to these components.
To add more groups to an existing restriction, select Add restriction again and select the same automation with the additional groups. You can also manage multiple restrictions at once: select the checkboxes on the left side of the restricted components and proceed with your changes.
If you add a group that's already included, Jira will ignore duplicates and only save new groups.
Removing automation restrictions
You can either remove a group from the restriction or remove the entire restriction:
- To remove a group from a restriction, next to the group name, select the delete icon
. If you remove the last group from a restriction, Jira will delete the entire restriction for that automation. - To remove all restrictions, next to the restricted automation, select the lock icon
. You can also remove multiple restrictions at once: select the checkboxes on the left side of the restricted components and then select the lock icon.
Configuring restrictions with REST API
You can configure a component with no allowed groups using the REST API. For example:
{
"restrictions": [
{
"componentKey": "jira.issue.event.trigger:transitioned",
"groupNames": ["jira-administrators"]
}
]
}This restricts all people except those in the jira-administrators group from selecting the jira.issue.event.trigger:transitioned component
Next steps
After you’ve configured automation restrictions, you might want to take a closer look at the automation activity and diagnose issues, if they appear. How to monitor automation activity