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,556,225
Community Members
 
Community Events
184
Community Groups

How to restrict what users see on the home Status Page

Hi team,

I am relatively new to StatusPage and my organisation is currently in the process of trialling internally before rolling out to customers. Because of the nature of our business and products, we have numerous components, and different customers will be interested in different components. As we're active across multiple markets globally, we even have different users within the same organisation who will be interested in different components (markets).

I have been doing some tests and found an issue (potentially user error on my part!). When a user is subscribed to a specific component, if I trigger an incident for that component, the notifications work perfectly. However, when I log into the home StatusPage as that user I see all previous Maintenance and Incidents, regardless of component. We only want users to see the history which is relevant to their component(s). 

Am I doing something wrong? Is this something we need to use audience specific pages for?

Thanks,

Chris

1 answer

1 accepted

0 votes
Answer accepted
Alan Violada
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 03, 2023

Hey Chris, thanks for reaching out to us with this question. Considering your use case, you are correct that the way to go would be using an Audience-Specific page - While you can control notifications on a per-component basis on other page types, audience-specific is the only page type that would allow you to limit which components each user has access to view in the page itself.

Manage audience-specific groups and users 

Let me know if you have any questions!

Regards,

Alan

Suggest an answer

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

Atlassian Community Events