Migrate Statuspage to use Atlassian accounts
Learn everything you need to know to migrate you and your team to Atlassian accounts.
Benefits of an Atlassian account
With an Atlassian account you can use just one account to log in to any Atlassian products, such as Jira, Jira Service Management, Confluence, Bitbucket, Opsgenie, Statuspage, and Trello. You don't need to manage separate accounts for each of these products - just one account to rule them all!
Moving to an Atlassian account also means more security and user management options, and Statuspage features like user permissions and the Jira integration.
The benefits of this migration are that users can:
Use the same credentials to access Statuspage and other Atlassian products.
Navigate more easily between Atlassian products with common navigation.
Manage team members across products, with unified Atlassian Administration.
Enable new security options (such as two-step verification, enforced password policies, etc.) with Atlassian Guard Standard (formerly known as Atlassian Access).
Use new integrations and features only available with Atlassian accounts:
Summary of changes
Account owners
What will change | What won’t change |
|---|---|
The account owner role becomes the Site admin role. Site admins manage the users and groups in Statuspage. They have access to the site's settings in Atlassian administration (admin.atlassian.com) and access to the products through this group. | Site admins have the same permissions as Statuspage account owners. |
Single sign-on will be set up and managed in Atlassian administration. You will no longer be able to configure Google Authentication or SAML single sign-on from the Statuspage management interface. | When single sign-on is configured with Atlassian Guard Standard, team member login is unchanged. Team members will continue to log in with the same identity provider. See more information about single sign-on and Atlassian Guard Standard in this documentation. |
There can be multiple site admins who have the abilities of an account owner. It’s no longer restricted to one person who can take these actions on your status page. |
|
Team members
What will change | What won’t change |
|---|---|
Team members will use Atlassian account credentials to log in to Statuspage (which we’ll help them create upon their first log in attempt post-migration). | When single sign-on is configured with Atlassian Guard Standard, team member login is unchanged. Team members will continue to log in with the same identity provider. See more information about single sign-on and Atlassian Guard Standard in this documentation. |
| Once team members log in, their experience in the Statuspage management interface is the same as it was before. |
Private and audience-specific pages
What won’t change |
|---|
Private and audience-specific page viewers are not affected by this migration and will view pages normally. |
User management
What will change | What won’t change |
|---|---|
User management will now be unified in Atlassian administration. | You still can do some basic user management in Statuspage such as setting user permissions. |
Email and password settings are managed in your Atlassian profile (id.atlassian.com). |
|
Only site admins will be able to invite new users to your Statuspage site (or give product access to existing cloud site users). Team members can send a request to a site admin to invite a new user. |
|
Only site admins will be able to revoke a user’s access to Statuspage. |
|
User management calls to our API can no longer be used to make changes to users or access the user list. Learn more |
|
Additional resources
To learn more about… | Read this |
|---|---|
Your Atlassian account | |
Security options with an Atlassian account | |
User management with an Atlassian account | |
Statuspage user permissions | |
Statuspage’s Jira integration |
Was this helpful?
Still need help?
The Atlassian Community is here for you.