Audience-specific status views (Agency)

Audience-specific views let one status page serve different slices to different people. An agency monitoring twenty client sites keeps a single internal page — and hands each client a private, unguessable URL that shows only that client's services and the incidents affecting them. Atlassian Statuspage sells this as "audience-specific pages" starting at $300/month; on CompleteStatus it is included in the Agency plan.

How it works

Each audience is a named subset of the page's monitors. Every audience gets a signed URL:

https://completestatus.com/status/{handle}/{slug}/a/{audience}?sig=…

The sig parameter is an HMAC signature covering the page, the audience and a per-page secret. That means:

• Links are unguessable — tampering with the audience key or signature yields a 403.
• Links are revocable — regenerating the page's audience links invalidates every previously issued URL at once.
• The audience view exposes only that audience's monitors, their uptime history and their incidents. Visitors never see the audience list, the other audiences, or the rest of the page.

Creating audiences

1. Open your page in the editor at /status-pages (Agency plan required).
2. In the Audience views card, enter a label — "Client Alpha", "Mobile team" — and tick the services that audience may see. Save.
3. Copy the signed URL from the audiences table and share it with that client or team.

Repeat per audience — a page can carry as many as you need. To remove an audience, tick Remove next to it and save; its URL stops working immediately.

Revoking links

Tick Regenerate all audience links and save. Every previously shared URL is invalidated and the table shows fresh ones — useful when a client offboards or a link leaks. (Removing a single audience only revokes that audience's link.)

Interaction with other access controls

• IP allowlist — still enforced on audience views: a visitor must be on an allowed IP and hold a valid signed link.
• Page password — not asked on audience views; the signed link is itself the credential. The full page keeps its password.
• Search engines — audience views are always noindex and never listed in the sitemap.
• Feeds/badges — the RSS/iCal feeds and badge cover the full page, not individual audiences.

Related guides

• /docs/status-pages — creating and configuring the underlying page.
• /docs/custom-domain-status-pages — serve the full page on your own domain.
• /docs/team-and-organizations — per-client workspaces, the other half of the Agency toolkit.