StatusPal
StatusPal.ioBlog
Documentation
Documentation
  • Introduction
  • Get Started
    • Key concepts
    • Step 1 - Configure services
    • Step 2 - Add your team
    • Step 3 - Personalize design
    • Step 4 - Enable notifications
    • Step 5 - Report an incident
  • Next Steps
  • FAQ
  • 1-Click Import
    • Atlassian Statuspage Importer
    • Status.io Importer (beta)
  • Platform
    • Services/components
      • Dependencies
    • Subscriptions & Notifications
      • Subscriptions
      • Notifications
      • Auto-maintenance notifications
      • Subscription Groups
      • Import email subscribers
      • Auto-subscribe to private status page
      • Custom email templates
        • Template examples
    • Incidents & Maintenance
      • Reporting an Incident
      • The Uptime Calendar Page
      • Custom Incident Types
      • Exporting your incidents
    • Information Notices
    • Private Status Page
      • Adding people to your status page
      • Access Groups/Audience Specific
    • Team Members
    • Status Page Settings & Design
      • Custom Domain
      • Advanced Settings
      • Design Customization
        • Design recipes
    • Multi-Language
    • Status Badge & Banner Widget
    • Integrations
      • Terraform
      • Datadog Metrics
      • Zoom Notifications
      • Google Analytics
      • Google Calendar
      • SendGrid Email Notifications
      • PagerDuty + Statuspal status page
      • Configure SSO for your status page with Okta
      • Configure SSO for your status page with Auth0
      • Configure your Mailgun Integration
      • Configure SMS Notifications (Twilio Integration)
      • Zabbix
      • Pingdom
      • Checkly
      • New Relic
      • Datadog
      • BetterUptime
  • Monitoring & automation
    • Out-of-the-box monitoring
    • Incident automation
    • Recurring maintenance
  • Security
    • Single Sign-On
      • Save your Recovery Codes
      • Configure Role provisioning from SAML attributes
      • Configure role provisioning for Okta
    • API Keys
Powered by GitBook
On this page
  1. Platform
  2. Private Status Page

Access Groups/Audience Specific

Access groups allow you to configure your private status page to adapt according to the audience visiting it.

PreviousAdding people to your status pageNextTeam Members

Last updated 1 year ago

You might have a status page with some services that should be visible to some customers, while other services should be visible to others, and admins should have the ability to manage all of them.

This comes particularly handy when you need to communicate incidents and maintenance to different customers, while in some cases some incidents or maintenance might affect multiple of their systems at once.

This can be achieved by configuring access groups for a private status page. You can access this feature by clicking on Members > Access groups from the sidebar of your status page.

Configuration

The following are the requirements to use Access Groups:

  1. You have invited your customers or stakeholders to your private status page as "viewer members" so they can access your status page.

Once the above is in place, visit Members > Access groups and click on "New access group".

You can select what services this group should have access to and who should be part of this group, granting them access to the selected services.

Any viewer member visiting your status page will only be able to see and subscribe to the services they have assigned to them via an access group.

A .

private status page
status page access groups for audience specific private status page
status page audience specific settings