We would want to offer separate status page per client.
Basically for every client we have separate infrastructure and separate monitoring metrics which we will feed into status page.
The status page should only be visible by the clients
What pricing option should we choose for this scenario.
Seperate public site per client or audience specific with multiple sections?
Hi @Dimitar Bojchev -
It sounds like using the Audience specific page would work in this use case. Each client would be a group that are affiliated with their own components/infrastructure. You can also configure the page to have separate metrics for each group. Here's how it could be set up:
Electronic Transcript Exchange
Audit Resource Center
Each client would be notified of an incident based on which components they are affiliated with. You can find more about Audience Specific pages here.
@Dimitar Bojchev Welcome to community.
I believe either solution would work but using the public site might be less overhead as you would not have to manage individual users access. Also since each customers infrastructure is separate there really is no reason to combine them.
I have also escalated to Atlassian so they can provide some additional insights.
We're excited to announce the release of a long-requested feature on Statuspage. Now visitors to your status page can subscribe to get notified in Slack when you report an incident or maintenance. Th...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events