How would you design a statuspage layout for multiple customers with their own specific subdomain?

Drew Arnold
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 7, 2023

We wanted to investigate/research how we would be able to setup a statuspage that would be accessible publically, but would be tailored for each of our customers.

 

We provide a SaaS solution where we provide them an account with a subdomain of their own choice.  An example of this would be customer1.example.com and another customer would have customer2.example.com.  We want to have these customers to both have statuspages for their site available and not to be able to view the other customer's information.  How should we design / layout these customer statuspages where our communication wouldn't need to be vague where they would contact our customer success team with whether their page is impacted.

1 answer

0 votes
Alan Violada
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 8, 2023

Hey Drew, Alan from the Statuspage Support team here.

The closest thing we have to the use case you provided would be the "Audience-specific" page type, which allows you to control what components each user has access to on a page, so that they only see the components that interest/affect them.

With that said, it is not possible to have multiple subdomains for one page - You would need a separate page for each customer for that, which would mean a separate billing plan for each one as well.

What are audience-specific pages? 

 

Regards,

Alan

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events