nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Audience-specific page question

Michael Monteiga_meds7r

Hypothetically, Product ABC is a SaaS solution. Each ABC customer's backend is individually hosted in AWS or Azure. ABC has grown tremendously and need a status page solution but does not want to have ABC customers knowing the status of other ABC customer's environments. The issue is this: ABC now has 200 customers and expects to eventually have thousands!

What is the recommended solution for this type of scenario?

Thank you in advance!

Accepted answers

All comments

Darryl Lee_2jimne

Hi @Michael Monteiga ,

This is Darryl. I am here to help.

From your description, it looks like you will need to have separated Audience Specific pages for individual ABC's customers to subscribe to without having access to any other customers. This plan is also scalable when the customer amount increases.

Here are some documents for your further reference:

Audience Specific page pricing and the details of the Audience Specific Page pricing

introduction of Audience Specific Page

What are Audience Specific Pages

Audience Specific Page Example

For more details, please feel free to contact Statuspage Support and my colleague will help you from there.

Hope this helps.

Kind regards,
Darryl Lee
Support Engineer, Atlassian

Majken Longlade_s1nhfx

To be sure - the recommendation here is a page per client? Rather than increasing the number of groups?

Darryl Lee_2jimne

Hi @Majken Longlade, yes, because the requirement here is company ABC doesn't expect each of the clients to know the status of each other's environment, so company ABC will need to subscribe and create individual Audience Specific Page for each of the clients.

Majken Longlade_s1nhfx

Thanks for confirming, maybe I'm misunderstanding how groups work? I had assumed that you'd be able to use components and groups to have multiple clients on one page, but segregate what they can see.

Though it's my understanding that there's a hard limit on components, so at some point you'd have to use multiple pages anyway?