Do I need a certain level of plan to access multiple pages?

[Tres Moore]

question about audience-specific pages or private pages - 

I have customers on their own tenancies and would like them to see their own version of my status page. We currently have the Hobby level (the $30/month) status page, but are looking to upgrade to whatever level we need to satisfy this need.

My questions are: 1) do you need a certain level of plan to add a new page? I don't see the option to add a page like Atlassian's support docs suggest.

and 2) would you recommend audience-specific pages or private pages for my use case? The product and components are the same

[Talar Pavlovic]

Hi there Tres! 

Thanks for writing into Community, I'm Talar from the Atlassian Statuspage support team, happy to help!

Let me answer each of your questions below and provide as much information as I can to help you make your decision. 

1) do you need a certain level of plan to add a new page? I don't see the option to add a page like Atlassian's support docs suggest.

• Nope! The access level you have to your Statuspage Org is what will affect your ability to create a new page: https://support.atlassian.com/statuspage/docs/what-user-permissions-can-i-grant/ 
• If you're not sure what role you have, please feel free to pop in a support ticket, share with us your Atlassian Site URL, or Statuspage page URL, and we can share with you more information 

2) would you recommend audience-specific pages or private pages for my use case? The product and components are the same

• The short answer is; it depends. Let me explain!
• It really depends on what you mean exactly when you said: "customers on their own tenancies and would like them to see their own version of my status page" 
  • If you need each of your customers to see a different stylised page, i.e. different colours, banner, etc, then I'd recommend separate Private pages for each. 
  • If you just need different customers to see different components, but happy for them to see the same stylised page (ie. same colours, banners etc), then I'd recommend an Audience-Specific Page 

Things to note for each page type: 

- Private Pages

• If you choose to go down the path of separate pages for each of your customers, there will more cost and more overhead, as you'll have to pay for each page separately, and update components across the pages separately. You can of course use the Statuspage APIs to make the incident creation/component updates more seamless. 
• However, since each page will be separate you'll be able to stylise each to make the requirements of each of your customers 
• You can see the different plan options for Private Pages here: https://www.atlassian.com/software/statuspage/pricing?tab=private 

- Audience-Specific Pages

• If you choose to go down this path, you'll have the 1 page to manage in the backend, and you can add all your customers into groups.
• You'll then assign each of the groups the components they should be able to see 
• When someone logs in, the page will look the same, except, they'll only be able to see the components you've allowed them to see 
• This page has a good example of how this works: https://support.atlassian.com/statuspage/docs/audience-specific-page-example/

I hope this helps! Please let me know if you have any further questions, and if you'd like to discuss anything related specifically to your account, please feel free to pop in a ticket any time. 

Kind regards,
Talar