Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Status page per client

Deleted user April 15, 2021


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?


Thank you

3 answers

1 vote
Gustavo Rivera February 14, 2022

We are using the Audience specific page. 

We have a multi-tenant application/platform. 

The components cover different features across all our customers.

BUT we desperately need to specify the customer group for an incident.  Sometimes any given feature only impacts specific customers.  And we want to drive the visibility and SLA of incidents based on a Incident <> Group relationship, to compliment the Incident <> Component relationship.

1 vote
Mark Campbell-Vincent
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 23, 2021

Hi @[deleted] -

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:


Client 1(Group):

Associated Components:

Transcript Services

Enrollment Reporting


Client 2(Group):

Associated Components:

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.

0 votes
Brant Schroeder
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 21, 2021

@[deleted] 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.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events