You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have two different pages in status page -- one internal and one external. I've separated the user accounts to have access to the internal page or the external page. But all users get notifications if, for example, a component on the internal page is set to something other than operational for a long time. How can I limit these statuspage warnings so they only go to the accounts that have access to the internal page?
Egor here with the StatusPage support team, thanks for reaching out!
It looks like your users are getting Long-running degraded component notifications. They are receiving these notifications as team members and not subscribers.
You can turn off these reminders, please see the following page to find out how to turn them off and additional info about notifications we send - https://support.atlassian.com/statuspage/docs/update-personal-information-and-notifications/
Please let me know if you have any other questions.
I wish you a beautiful day ahead.
Hey, Egor. I'm getting a 404 at that link above.
Yes. that's right. The team members are getting notifications and I'd like to be able to adjust those. We had team members who had no access to a certain status page receiving those notifications. We have a couple status pages in our instance and groups of members for each.
There was a white space in the link. Please try to use the following one - https://support.atlassian.com/statuspage/docs/update-personal-information-and-notifications/
I'm afraid that you cannot adjust notification preferences for other users and each affected person should follow the steps described in the article to adjust it.
You can have multiple pages on your org, but team members (admins of SP) have access to all of your pages and have control over your components/incidents, and so on.