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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Can you disable Statuspage 'Unsubscribe' button in MS Teams channel?


My organisation is trialing the use of the Statuspage app within MS Teams, whereby our intention was to subscribe a channel eg. 'Unplanned Disruption' announcement channel so that all users within that Teams space can see system incident notifications via that channel come through from Statuspage while using MS Teams.

However, after successfully getting the app setup in MS Teams and the Statuspage webhook setup for the channel, and successfully testing incident notification messages coming into the channel, we noticed each message comes with an 'Unsubscribe' button that appears to all users of the channel.

But it seems clicking this option asks the the user (any user) if they want to unsubscribe the webhook from the channel. We plan to have over 150+ people using this channel and we want to avoid a situation where our users unsubscribe the webhook and effectively turnoff Statuspage notifications for everyone in that channel...

Is there a way for us to disable the 'Unsubscribe' button that appears? While we can communicate to our staff to ask them to please not unsubscribe the Webhook, there is no guarantee someone might not still unsubscribe it by accident - so we would prefer the button not be accessible to everyone in the channel.



1 answer

0 votes
Connor Eyles
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 12, 2021

Hey @Matt Lane 

Hope you are well! 

I understand that wanting to remove the unsubscribe button would help with removing the possibility of your users from unsubscribing from updates but unfortunately, we do not own the Microsoft teams Integration app so we are unable from making changes on that one.

I will also like to note our subscriptions mechanism
was built under the philosophy that the recipient is the one that has total
control over what information they do or do not receive. If someone chooses
to unsubscribe, or to tune their settings so they don't receive
notifications from specific components, we need to respect that choice.
This decision is reinforced by anti-SPAM laws and our product most commonly
being used as a Public offering where anyone can signup for notifications,
so we wanted to protect users from abuse.


Thanks Connor, appreciate the answer on this. Any idea if Microsoft might be receptive to this type of customisation in future - re: these type of buttons / being able to hide in channel if channel owner wants?



Darryl Lee
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 07, 2022

Hi @Matt Lane,

Unfortunately, we are not able to know if this is on the roadmap on the Microsoft side, please consider reaching out to Microsoft Support via this link.

Meanwhile, I have also created a feature request for this requirement, STATUS-453, to gather more attention internally.

Please note that the feature request doesn't provide visibility to our customers so I don't attach the link here.

Please note that our Product team reviews all Feature Request (FR) together and they prioritize those with higher demand to be implemented first and any FR will take months until is ready since it needs to go through Design, Development, Testing, and rolling out to Production.

Thank you very much for your feedback in helping us improve Statuspage.

Kind regards,
Darryl Lee
Support Engineer, Atlassian

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events