Restrict certain information to certain external customers

[Muttitt, Paul]

Is there a way to show the status of your systems to anyone who signs up, but then show additional information to only certain users?

[Siddhartha Mohapatra · Accepted solution]

Hello Muttitt,

G'day! I hope this message finds you well. Thank you for contacting the Atlassian Community! I am Siddhartha from the Atlassian support Team.

If you're looking to provide a basic status to everyone while keeping specific details restricted, consider using an Audience-Specific page. This approach allows you to manage group and component access effectively. Remember, all users need to be authenticated and assigned to groups, as there is no option for a public or self-service model where some users can see more than others simply by signing up.

It's important to note that Atlassian Statuspage does not support displaying a basic system status to any authenticated user while offering additional information only to select users on a single page. However, you can achieve a similar effect through Audience-Specific pages, albeit with certain limitations.

1. Public Pages

• Anyone can view the status page and see all incidents, maintenance, and component statuses.

• On a public page, additional information cannot be restricted to only certain users; it is visible to everyone.

2. Private Pages

• Only authenticated users (via SSO/SAML or Google Auth) can view the page.

• All authenticated users see the same information. There is no way to show more information to some users and less to others.

3. Audience-Specific Pages

• Every viewer must authenticate (no anonymous access).

• You can assign users to groups, and each group can be granted access to specific components.

• Incidents and maintenance events are only visible to users/groups who have access to the affected components.

• If a user does not have access to a component, they will not see incidents or maintenance related to it.

• You can create a group that has access only to "basic" components (e.g., "Overall System Status") and assign all users to this group. Then, create additional groups for privileged users with access to more detailed components.

• However, all users must be explicitly added and authenticated. There is no "sign up and see the basics, but only some see more" in a seamless, self-service way.

4. What you cannot do

• You cannot have a page where anyone can sign up and see a basic status, but only some users (based on group or role), unless you use Audience-Specific pages and explicitly manage group membership.

• There is no "progressive disclosure" model in which users see more as they are promoted or assigned roles, unless you manage this via group assignments in Audience-Specific pages.

How to Achieve a Similar Effect

• Audience-Specific Page Setup:

  1. Create an Audience-Specific Statuspage.

  2. Create a "basic" group with access to only the general components.

  3. Create additional groups for users who should see more detailed components/incidents.

  4. Assign users to groups as needed.

  5. When an incident or maintenance is created, associate it with the relevant components. Only users/groups with access to those components will see the details.

Authentication:
All users must authenticate (via SSO/SAML or username/password). There is no anonymous or "just sign up" access.

Summary Table of page type | Viewers | Auth | 

Page Type	Anyone can view?	Auth required?	Per-user/group info visibility?	Use case for your scenario?
Public	Yes	No	No	❌
Private	No	Yes	No	❌
Audience-Specific	No	Yes	Yes (by group/component)	✅ (with group management)

Thank you
Siddhartha
Atlassian Support