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,462,577
Community Members
 
Community Events
176
Community Groups

Notify Audience-specific incidents

We're developing a platform that's currently being deployed on-premise to a growing count (hundreds) of sites.

We're looking for a platform that will allow us (the providers) to display to the site's owner the status of their own on-premise deployment, including an ability for us (the providers) to display a dedicated message for them.

That means the same template, but a unique instance of Statuspage for each site.

 

e.g: site X is operating perfectly, but site Y is currently experiencing connectivity issues with one of our services.

When site Y's users go to their status page, I want them to see a message from us, but site X shouldn't see it.

 

I tried reading more about Statuspage's audience-specific page but didn't see any mention of that use case.

Is that a use case supported by Statuspage?

1 answer

0 votes
Abraham Atlassian Team Dec 30, 2021

Hey Ben,

Abe here with Statuspage support. That is a good use case for Audience-Spesific. Users will only see components/components groups they are assigned.

In your case, making one component site X and another component site Y. If site Y is down, only users with access to the component that corresponds to site Y will see that. Users with access to the component that corresponds to site X will not see anything for Site Y as ling as they don't have access to the component. 

Hope this helps! 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events