Will users from an SSO enforced domain be able to log into the Hobby version of Statuspage?

[Belinda M]

If I have Atlassian Guard set up for my company where users with our domain are forced to log in via SSO, then I decide to purchase the Statuspage Hobby subscription for just a few of our users, will they then have an issue when trying to log in?

[Talar Pavlovic]

Hey Belinda! 

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

Before I answer, let me provide some context, because Statuspage is a little unique in the way it works.

Statuspage has 2 different User Interfaces: 

UI 1 = the Statuspage Admin Panel (https://manage.statuspage.io)

This is where users log in to administer the page; e.g. create a new incident, or send an update 

UI 2 = the Statuspage Itself (<page>.statuspage.io)

This is the page itself, where your users or customers will go to see the status of components, or see if there is an incident posted. 

There are 3 different Page Types in Statuspage: 

1. Public: anyone with the URL can access this page (e.g. https://metastatuspage.com/)
2. Private: users will need to be given access to the page and can access it via Username/Password, SSO or IP Allowlists (depending on the setup). Once logged in, the user can see everything on the page (that is; all components, incidents etc). 
3. Audience-Specific: users will need to be given access to the page and can access it via Username/Password, SSO or IP Allowlists (depending on the setup). Once logged in, the user can see only components (and associated incidents) that are assigned to them - as an example: the page could have Comp1, Comp2, Comp3, but the user can see only Comp2. 

Where does Atlassian Guard come in to play?

When Atlassian Guard is setup on the Atlassian Org containing Statuspage, team members who are given access (from https://admin.atlassian.com) to Administer Statuspage (via https://manage.statuspage.io) will be able to log in via your Atlassian Guard SSO setup.

A Hobby page, is a Public page, so no authentication is required to view the page itself (<page.statuspage.io). 

If you were to switch to a Private or Audience-Specific page though; whilst Guard would still take care of login to the Admin Panel, SSO login to the page itself would need to be setup separately: 

• IP Allowlist: https://support.atlassian.com/statuspage/docs/set-up-ip-allowlisting-authentication/
• SAML for Private Pages: https://support.atlassian.com/statuspage/docs/require-saml-for-private-pages/
• SAML for Audience-Specific Pages: https://support.atlassian.com/statuspage/docs/require-saml-for-audience-specific-pages/ 

Hope this helps!
- Talar