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

Differentiate alerts sent across subscriber segments

We have certain subscribers who would like to be notified of every tiny incident happening on our application.

As we don't want to alert all our subscribers of every tiny incident but would like to alert these specific people, we would love to differentiate between subscribers.

I however can't find this option. Am I overlooking something or are there workarounds that could help me doing so?

Thanks in advance for the information.

Kind regards,


1 answer

1 vote
Jesse Klein Atlassian Team Jun 23, 2021

Hello Rydoo,

This is Jesse from the Statuspage support team. One of the options is to use component subscriptions:

You can select which components people subscribe to and then people that only care about certain components can to subscribe to just them while leaving everyone else that wants to subscribe to everything can also do so. This requires a business plan, however.

Beyond that, you could turn on the feature to allow users to subscribe to individual incidents. Under Subscriptions, you can go to Options > Settings to make this change. This allows users to subscribe to incidents after the incident starts.

Hopefully one of these options could help you out!

Thanks for the insights!

Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events