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
  • Restrict by network IP
  • Restrict access to members
  1. Platform

Private Status Page

Configure a status page to be restricted only to authenticated users or to specific network IPs.

PreviousInformation NoticesNextAdding people to your status page

Last updated 5 months ago

In order to configure a status page to be private/restricted, you can configure it under your status page settings (Click on Status page in the sidebar) in the "Privacy" section.

Restrict by network IP

In the first text field, you can enter comma-separated list of IPs or IP ranges. Once configured, only those IPs in the list will have access to the status page.

Restrict access to members

Upon checking this checkbox (and clicking on Update), only members with permission to the status page will be able to visit it.

Unauthenticated users will be greeted by a "Sign-in" page which prevents access to the status page without authenticating.

In StatusPal, there is a special member role called "Viewer," which grants a user viewing access to a status page or organization.

Each subscription plan comes with as many viewer members as subscription seats, which makes StatusPal much more affordable than competitors.

Automatically subscribe your private status page users as they get added. Learn more at Auto-subscribe to private status page.