Using multiple authentication types on private pages
Asked by Dragan Markovic:

I'm currently evaluating StatusPage and was wondering if the following is possible:

Requirements:

- Private page only not visible to public   
- We use azure SSO for internal domain users   
- We also have number of partners not on our domain that will need access to the same page

Is it possible to have both SSO and Atlassian authentication for the same page or how would we go about accomplishing this? Not sure if we would need another Audience specific page to do this and does that mean we have to manage two pages simultaneously?

Thank you


Answers:
author: Muhammad Zeeshan
body: Hey Dragan,

For page-viewers it is not possible to have multiple forms of Authentication for a Private Statuspage subscription. Please see our documentation to learn how you can set up Authentication for Private Pages: <https://support.atlassian.com/statuspage/docs/require-saml-for-private-pages/>

BR,

comments: author: Dragan Markovic
body: Thank you very much. With that being said I am using Trial mode which does not allow multiple pages to be created so i can't test the following scenario; if i was to create another audience-specific page using Atlassian authentication, would incident management and status changes be managed separately on each individual page? Or would we be able to create incidents, send updates, change statuses for Private page and have the same reflected on the audience specific page/group notifications.


author: Muhammad Zeeshan
body: For two separate pages all the configurations and incidents will be managed separately.


author: Dragan Markovic
body: Thank you very much !


author: Muhammad Zeeshan
body: You're most welcome! ??


author: Rafael Meira
body: Hey Dragan,  

Within your Statuspage organization, you create as many public/private/audience-specific pages within it as you'd like. When logged into manage.statuspage.io you select the page in the top left to open a drop-down to navigate between your organization's pages and add another page.  

I will send below a few links on specific topics like page types, and how our SSO works in general.  

**User level and Different types of pages**   
[Add a New Page](https://support.atlassian.com/statuspage/docs/add-a-new-status-page/)   
[Free Trial](https://support.atlassian.com/statuspage/docs/what-do-i-get-on-a-free-trial/)   
[User level - Adding new users](https://support.atlassian.com/statuspage/docs/what-user-permissions-can-i-grant/)   

**SSO**   
[Require SAML for audience-specific pages](https://support.atlassian.com/statuspage/docs/require-saml-for-audience-specific-pages/)   
[Require SAML for private pages](https://support.atlassian.com/statuspage/docs/require-saml-for-private-pages/)   

**Basics**   
[Statuspage Basics](https://support.atlassian.com/statuspage/docs/read-the-statuspage-user-guide/)   

Best,  
Rafa

comments: author: Dragan Markovic
body: Thank you very much. With that being said I am using Trial mode which does not allow multiple pages to be created so i can't test the following scenario; if i was to create another audience-specific page using Atlassian authentication, would incident management and status changes be managed separately on each individual page? Or would we be able to create incidents, send updates, change statuses for Private page and have the same reflected on the audience specific page/group notifications.