Status page per client

[Deleted user]

Hello,

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

[Gustavo Rivera]

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.

[Mark Campbell-Vincent]

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.

[Brant Schroeder]

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