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,456,333
Community Members
 
Community Events
176
Community Groups

Status page per client

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

3 answers

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.

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:

 

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 Apr 21, 2021

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

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events