Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,554,323
Community Members
 
Community Events
184
Community Groups

Simplifying notification for multiple recipients upon new page creation

Edited

We have a Confluence Cloud implementation with upwards of 50 users spread across engineering, product management, client implementation projects, and customer service.

When a developer on my team publishes a page to Confluence (typical use case is that of a release notification), I want them to notify other Confluence users -- approximately 25 of them.  And it's quite error-prone and inefficient to list out the 25 people by their handles.

Now, all of these people are available on Microsoft Teams.

Is there a way to:

  1. EITHER Create a distribution list from within Confluence so that all required recipients get notified through a single handle,
  2. OR push an event to Teams via a webhook so that I can manage the recipients list on Teams. They can click through and access the Confluence URL from the Teams channel?

I've already tried setting up MicrosoftTeams Confluence Connector Lite (https://solutionsbytext.atlassian.net/wiki/marketplace/discover/app/confluence-microsoft-teams-connector-lite) but that doesn't send alerts for new page creations: it sends out alerts only for page updates.

Any suggestions?

Edits:

  • We are using Confluence Cloud

1 answer

1 accepted

0 votes
Answer accepted
Connor
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Apr 26, 2023

Hi @Chiranth I can think of a few methods, some better than others. 

  1. Add all of the desired users to the Watchers list of each Space that pages will be created in.
    • Note: Users can remove themselves from watching a Space, so this might not be ideal.
  2. Create a Team that includes all the users you want to notify. Then you have these options available to you, which I've ordered from best to worst in my opinion.
    • When creating a new page @mention the Team on the page
    • After creating the page, click the blue Share button, and share the page with the Team.
    • After creating the page, @mention the Team in a page comment.
    • Note: downside to this is your users would need to remember to @mention or share the page.
  3. Create an automation rule that triggers when a page is published and sends an email to the desired users, or sends a message to a Microsoft Teams channel via webhook.
  4. Install the Atlassian official Confluence Cloud for Microsoft Teams app (This option would coincide with option 1 above)
    • Instruct all of the desired users to configure the notification settings of the Confluence Cloud for Microsoft Teams app and enable the Page created in a space you're watching notification.
    • Note: This has the same negative as option 1 above, plus also requires each user to configure the notifications for the Confluence Cloud for Microsoft Teams app.
    • I do recommend using this official app though, I have personally found it useful for keeping track of changes in Confluence.

In my opinion, I think a combination of option 2 and 3 is the easiest to setup and manage. The Atlassian team you create can be used in Jira/JSM and other Atlassian products, so you could get more functionality out of it than just page notifications. And option 3 would ensure the notification (email and/or Teams message) gets sent, without having to rely on users remembering to @mention or share the page with the team.

Connor, thank you so much for your detailed response.

I've gone ahead with Option 2 for now. 

Thanks again!

Like Connor likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events