Access, Domains, and Organization Management

StatiBeat intentionally separates tenant-wide administration from page-specific operations.

The two main admin layers

Organization admin

Use organization admin for:

• status page creation
• billing
• tenant users
• organization-wide authentication
• page directory management

Page admin

Use page admin for:

• incident and maintenance operations
• page customization
• hierarchy and component setup
• subscribers
• routing and viewer access
• integrations and automation

Page routing and domains

The page routing screen controls:

• URL prefix
• public vs private visibility
• viewer access mode
• managed custom domain

That makes it the place where public URL design and viewer authentication come together.

Viewer access modes

Private pages can be configured with:

• shared password
• viewer SSO
• shared password or viewer SSO

Viewer authentication is for people reading the page, not for admins using /admin.

Page roles and page membership

Page access controls who can operate a specific page.

Common patterns:

• viewer for visibility only
• manager for day-to-day workflow control
• admin for configuration ownership

If advanced RBAC is enabled, custom page roles can split those responsibilities more precisely.

Organization-level user and auth management

Organization admin also covers:

• creating tenant users
• granting org-admin membership
• managing billing state
• configuring OIDC or SAML for admin sign-in
• mapping groups to page-scoped roles when supported

Practical governance advice

• Keep page ownership separate from tenant ownership where possible.
• Decide who owns billing, page creation, and authentication centrally.
• Decide who owns incidents, customization, and day-to-day operations per page.
• Treat domains and viewer-access rules as part of launch readiness, not cleanup work for later.