Automation basics
Understand the general concepts and best practices of automation in Atlassian cloud products.
Automation is available with Confluence Premium and Enterprise.
Site admins and Confluence admins can turn automation rules on and off, copy them, or delete them at the global level. Space admins can turn rules on and off, copy them, or delete them for individual spaces.
While you may not think of yourself as an admin, if you have a personal space you’re an administrator of your space!
This includes the rules tied to smart buttons. When a smart button’s rule is turned off or deleted, it will not work and users selecting it will see an error message.
To navigate to Global automation:
Only site admins and Confluence admins can view Global automation.
Select the wheel icon () in the top-right corner to open Confluence administration.
Find Admin tools in the left-hand navigation.
Select Automation.
To navigate to space automation (space admins):
Go to the space where you’d like to manage your rules.
From the sidebar, select Automation.
Select Rules from the Automation card.
To access space Automation from a page (space admins):
Go to a space where you're an admin.
Open a page in view mode.
On the top right toolbar, select the lightning bolt icon or press a.
If you don’t see Automation in Confluence administration or Space settings, this might be why:
You're on the Space Overview page, a whiteboard, or a database. The automation icon appears only on pages in view mode.
You’re not an admin of the space you’re in (for Space automation).
You’re not a site admin or Confluence admin (for Global automation).
Your team has Cloud Standard or Cloud Free – automation is a premium feature in Confluence.
Once you’re in Global automation or Space automation, your options to manage rules are the same. You can turn a rule on or off, copy a rule, label a rule, or delete a rule.
Site admins can disable the ability for space admins to edit rules. If you don’t have edit access to your space’s automation rules, contact your site admin.
The top of the list of rules provides several ways to filter it.
Search field: Enter text to filter by the names of your rules.
Scope: Choose to view All rules, Global rules, or Space rules.
Action: Find rules that include a specific action. Choose from a drop-down list or search by the action’s name.
Labels: Select the Labels button to filter rules by a specific label.
Each rule has a toggle to enable it. Turning the rule off in Global Automation will turn it off for all sites. Turning a rule off in a space only affects that space.
Select the more actions menu (ellipsis icon).
Select Delete.
Confirm that you want to delete the rule by selecting OK.
If you delete a rule connected to a smart button, all copies of that button on any page or blogpost will stop working.
Select the more actions menu (ellipsis icon).
Select Copy.
The rule-builder opens with a copy of the rule. You can modify any component.
When you select Turn on rule, you will need to give it a uniwue name.
Select the more actions menu (ellipsis icon).
Select Export.
A .json file will download to your computer. It contains the code used to run the rule.
To apply a label to a rule, click the space under the Labels column.
A list of labels opens, along with a text field to create a new label.
The Edit labels button in the table header lets you modify the name or color of any label.
Each of your rules will have an audit log that you can review to see when the rule was triggered, the final result of the execution, and any actions that may have been performed in the last 90 days.
Select the Audit log tab to view the last 90 days of activity in your space or Global Automation (depending on your admin level).
For each rule execution, the audit log will display:
Date: the date and time that the rule was triggered.
Rule: the name of the rule.
Status: the status of the rule execution.
Duration: the length of time the rule took to execute.
Operations: the actions that the rule performed and any associated items.
You can view the audit log of an individual rule, at the project/space level, or for all rules in a product. Reviewing your audit logs is an effective way of debugging your rules.
Note that audit log entries are stored for 90 days; entries older than this are removed from the log and can't be recovered.
Was this helpful?