Set up private status pages with Atlassian Groups
Private status pages are available on Service Collection Enterprise plans.
A private status page restricts who can view your status page. Unlike a public status page, which anyone with the URL can open, a private status page requires each visitor to sign in and be verified as a member of a linked Atlassian group before they can see incident updates, maintenance notices, or service health.
This is useful when your status page is for a known audience - internal staff, or a specific set of customers or partners - rather than the public. A single Jira Service Management site can host multiple private status pages, each linked to a different group, so you can serve different audiences from the same instance.
How a private status page controls access
When someone opens a private status page URL, they are redirected to sign in. After they authenticate through your identity provider, the system checks whether they are a member of the Atlassian group linked to that page:
If they are a member, they are granted access and see the status page.
If they are not a member, they see an access-denied message and cannot view the page.
Visitors do not need to create an Atlassian account or register as a portal customer. Authentication is handled through your organization's SAML single sign-on (SSO) configuration - the same one used for your Jira Service Management portal.
Before you begin
You need organization admin access in admin.atlassian.com to manage Atlassian groups, and Jira product admin access to configure status page settings.
Your organization must have an Atlassian group set up, with members synced from your identity provider (for example, Microsoft Entra ID, Okta, or Google Workspace) using SCIM.
The group you want to use must already exist and contain the people who should have access.
SAML single sign-on must be configured for your organization, because private status pages reuse that authentication policy.
Step 1: Confirm your Atlassian group
Before you link a group to a status page, make sure the right group exists and contains the correct members.
Go to admin.atlassian.com and select your organization.
Go to Directory > Groups.
Confirm the group you want to use exists and has the correct members. If you need to create a group or sync members from your identity provider, do this before you continue.
If your organization uses SCIM sync, group membership stays in sync with your identity provider automatically. Adding or removing a user in your identity provider is reflected in Atlassian without any manual change.
Step 2: Create the private status page
In Jira Service Management, go to Operations > Status pages.
Select Create status page, then choose Private.
In the status page settings, open Advanced settings and find the Access section.
Search for and select the Atlassian group whose members should have access.
Select Save.
You choose whether a status page is public or private when you create it. Confirm the page type before you save - the page type cannot be changed afterwards.
How visitors access the page
Share the status page URL with your intended audience.
When a visitor opens the URL, they are redirected to sign in.
The visitor authenticates with their corporate credentials through your identity provider.
The system checks whether they are a member of the linked group. Members are granted access; non-members see an access-denied message.
Manage access over time
To change who can view a private status page, update the membership of the linked group in your identity provider. If SCIM sync is configured, the change is reflected automatically and you do not need to change anything in Jira Service Management.
To link a different group:
Go to Operations > Status pages and select the status page.
In the Access section, select a different Atlassian group.
Select Save. People in the previous group lose access immediately; people in the new group gain access on their next visit.
If an organization admin deletes a group that is linked to a private status page, members of that group lose access to the page.
Subscriptions on private status pages
Subscribers to a private status page receive email notifications when you publish incident or maintenance updates, the same as a public status page. Two things work differently:
Only signed-in members of the linked group can subscribe themselves.
A product admin can manually add subscribers on behalf of people who have given consent.
If you remove someone from the linked group, they lose access to view the page, but their email subscription is not removed automatically. To stop the notifications, remove their subscription manually from the Subscriptions tab in the status page settings.
Troubleshoot private status page access
Issue | What to do |
|---|---|
A user can't access the page after signing in | Confirm the user is a member of the linked group in admin.atlassian.com > Directory > Groups. If you use SCIM sync, confirm the sync has completed and the user appears in the group. |
The group dropdown is empty when you configure the page | No Atlassian groups exist yet, or none have been synced. Go to admin.atlassian.com > Directory > Groups to set up a group first. |
A user is sent to the wrong sign-in page | Private status pages use the same SAML single sign-on policy as your portal. Check your authentication policy in admin.atlassian.com > Security > Authentication policies. |
A former employee can still access the page | Remove the user from the linked group in your identity provider. If SCIM sync is configured, the change propagates automatically. Also remove any active email subscription they hold. |
A removed user still receives notifications | Removing a user from a group revokes viewing access but does not cancel their email subscription. Remove the subscription manually from the Subscriptions tab in status page settings. |
Was this helpful?