Avinoam from Confluence Automation here with an exciting new feature to make it easier for end users to use Automation for Confluence.
With smart buttons, end users on Confluence Premium and Enterprise plans are now able to create their own rules from a pre-defined list and run the automation with a click of a button on the page. This helps admins and users save time by safely placing automations in the users' hands, with the right guardrails. Let’s dive in!
We know being an admin isn’t easy, especially when juggling multiple requests across spaces, assigning new users, and more. Smart buttons helps reduce the admin burden by allowing users to set up and launch one-time automation rules on a specific page.
It’s a win-win for all: admins get time back to focus on other high priority work, end users can eliminate low-value manual tasks, and everyone benefits from the clearer processes that smart buttons enable.
Create a “Send for approval” smart button on a creative brief: Once clicked, it will change the page status to “ready for review” and send an email to reviewers with a request to approve the details.
Create a “Notify team members” smart button on a marketing launch plan: Once clicked, it can update page restrictions so cross-functional partners can access the plan and send an email to share it with them.
Create a “Kick off next steps” smart button on a product poster page: Once clicked, it can add a label for the new product and create new page templates for product requirements, product design, and technical documentation to be filled in by the team.
To help improve team processes and workflows, admins can add smart buttons to new or existing page templates. For example, adding in a “Approve project poster” smart button to the “product requirements” template, so end users can simply click the smart button when ready to trigger approval workflows.
Admins will be able to view and manage all smart button automations in Global automation or Space automation. These automations will be identified by a smart button
label, and admins will be able to view it in the rule builder, as well as disable it as needed. They’ll also be able to see page details in the audit log to see where the smart button was triggered.
When ready to add a smart button in edit mode, end users can select the insert menu (+ icon) from the toolbar or type /smart button
or and select “smart button.” From there, the end user can choose from a pre-defined list of automation templates and edit the components to fit their use case.
Anyone with view permissions on a page can hover their cursor over the smart button to see what actions it’ll take. When a user clicks the smart button, it’ll trigger the actions in sequence, respecting the permissions they’ve been assigned. For example, a user who has edit access can successfully run a smart button to change a page’s status and update its labels. However, a read-only user will still not be able to change the page’s status or labels, even through the smart button. This helps set safeguards in place and control who has access to run the automation.
It's currently rolling out gradually to all Confluence Premium and Enterprise admins and their users!
We’d suggest admins start by adding smart buttons to page templates and promote these pages, making it easier for end users to understand how smart buttons work before they start creating their own.
Admins can also work with power users to help identify the top use cases and guide them through the first smart button setup. Questions to ask would be: Are there any workflows that require repetitive manual tasks? What tasks are involved (e.g. notifying team members, adding a label, updating page status)? What type of pages are typically involved?
Only smart button usage that successfully takes an action will count towards your overall automation usage. Admins can manage automation usage by determining which users can create automations, as well as by monitoring top-running rules from the Automation Usage tab. Automation Service Limits will also apply across smart button usage.
Great question! Last year, we released manual triggers as our first foray to opening Automations in Confluence to end users. However, unlike smart buttons which can be created by end users directly, manual triggers need to be pre-defined and set up by admins in order for end users to trigger them.
In addition, smart buttons can be added anywhere inside a page within the context of the content, whereas manual triggers exist at the entire page level and not in context.
This is just the beginning of smart buttons! Over the next few months, we’ll continue to add more use cases and actions for smart buttons, including actions across other Atlassian products like Jira. We’ll also provide increased levels of visibility for admins, making it easier to manage all smart buttons built by end users.
We’d love your feedback so please feel free to schedule time with us directly here or drop a comment on this post on how you plan to use smart buttons!
Avinoam
Principal Product Manager, Confluence Cloud
10 accepted answers
15 comments