Skip to main content

Application Overview

This page is a quick map of the product surfaces that exist in the current application.

Use it as a navigation guide, not as the deepest source of truth for each workflow.

tip

If you already know what you are trying to do, the task-based guides in the sidebar are usually more useful than this overview page.

Public status page​

The public experience includes:

  • a homepage with overall status, hierarchy, incidents, maintenance, and previous activity
  • host-based routing and explicit /status/<url-prefix> routing
  • service, incident, and maintenance detail pages
  • private-page access gates for shared password and viewer SSO when a page is not public
  • subscriber and self-service management routes such as /subscribe, /manage, and token-driven management actions

The frontend routes for these flows are wired in application/frontend/src/App.jsx.

Read next:

Setup and sign-in surfaces​

The current SPA also includes:

  • first-run setup at /setup
  • admin sign-in at /login
  • password reset request and confirmation flows
  • admin SSO callbacks
  • Slack account-link confirmation routes

These are also defined in application/frontend/src/App.jsx.

Page administration​

The page admin navigation currently exposes these areas:

  • overview
  • incidents
  • maintenances
  • preset messages
  • Beats
  • hierarchy levels
  • hierarchy items
  • incident lifecycle
  • maintenance lifecycle
  • status types
  • variables list
  • view alias blocklist
  • custom views
  • RSS feeds
  • subscribers
  • customization
  • domain and viewer access
  • config status
  • AI
  • auditing
  • API tokens
  • access
  • Slack app
  • Terraform

These sections are defined in application/frontend/src/constants/adminNav.js.

The page-admin workspace also includes:

  • the admin search palette for jumping between available screens and setup guides
  • the read-only admin assistant drawer for natural-language help on supported workflows

Several page-admin areas are feature-gated or plan-gated. In the current application:

  • Beats requires synthetic monitoring
  • Slack App requires the Slack feature
  • Terraform requires the Terraform feature
  • Auditing requires audit-log support
  • some custom-view and RSS flows depend on plan limits rather than a simple on or off feature flag

Read next:

Organization administration​

Organization-level administration currently exposes:

  • overview
  • billing
  • status pages
  • users
  • authentication

These entries are defined in application/frontend/src/constants/orgAdminNav.js.

The org-admin workspace also includes its own search palette and can route directly into an accessible page-admin workspace when an operator needs to move from tenant setup into day-to-day page operations.

Read next:

Public self-service and management flows​

The application also exposes self-service routes for:

  • subscriber access links and subscription profile management
  • custom view management
  • RSS feed management
  • token-based manager access to views, feeds, and subscriptions

These flows are backed by the scoped public and management routes in application/backend/cmd/server/routes.go.

Read next: