Can "smart button" be added to different sections of a template page to trigger different actions?

[Yu Zhang]

Questions:

1. Use Cases of Automation in Confluence:

   • What are some use cases of automation designed to suit different purposes within various sections of a Confluence page, without using additional add-ons?
   • How can I set up multiple 'smart buttons' across the page, each dedicated to a particular section, and perhaps different buttons for different user groups to leverage (that may trigger corresponding actions)?
   • Would setting up these smart buttons require different content macro designs?

2. User Group Setup for Email Notifications:

   • How can user groups be set up in Confluence to tailor email notifications associated with certain actions within the page?
   • If fully integrated with Jira, does the user group setup in Confluence need to align with the Jira user group settings?

[Andrea Tagliabue]

Hi @Yu Zhang

welcome to community!

1

• the use case are multiple depends the achivement you want to reach, there too many add-ons to suggest one without context
• You can't set different permission level inside a page. a page is visible entirely or not.
• yes you can configure different macro, here the guide

2

• confluence doesn't have project/space roles, so you have to handle the notifications via groups in the admin section
• depends if the confluence users have to login in jira. jira and conflu are 2 different apps with different billing user based, as per best practice you should keep the app access distinct in order to have full control on user's licenses. for exemple user A in order to access to jira have to be in the group jira-software-users-site-name and in order to use confluence in the group confluence-users-site-name

[Evie Z.]

This topic is now closed as the discussion has become outdated. If you have more questions or want to continue the conversation, feel free to start a new topic. For more details on why we close older threads, check out our Rules of engagement - Atlassian Community .

Thank you for your understanding!