Client Status Pages

Use Status pages in the app to create a page for a selected client and choose the monitored assets to publish as components. Anyone with the public URL can view it without signing in. Review the preview and the published page before sharing.

Choose the correct kind of link

A legacy token link is not a client-specific link. Do not send it to an individual client unless every item it exposes is appropriate for that recipient. Creating a client page does not change or revoke an existing legacy link.

Create, preview, and publish

1. Open Status pages and create a page for the intended client. You can also reach this area from that client's detail page.
2. Set the page title and slug.
3. Add the assets you want viewers to see as components. The app's asset picker shows the selected client's assets.
4. Inspect the private preview, including component names, domains, incident text, and maintenance details.
5. Publish the page and open its public URL in a signed-out browser before sharing it.

The published component list determines the page's asset scope. A client name alone does not filter components added through the API: the API accepts assets belonging to your workspace. Check every component when using an integration or editing an existing page. Pages do not grant access to the dashboard, billing settings, or other workspaces.

Vendor stack tags are workspace-wide context, not proof that an incident affects a particular client. Confirm relevance before adding vendor details to a client page or incident update.

Plans and branding

• Free: create one status page per workspace, with the Merlonix badge.
• Starter: an existing Free page keeps its URL and loses the Merlonix badge. You can edit it, but Starter does not include new page creation.
• Team and above: create client status pages, with one page per client.

Removing the Free badge does not remove all Merlonix attribution or enable a custom domain. The separate white-label add-on is available on Agency, Compliance, and Enterprise subscriptions and enables custom-domain status pages. See white-label reports for its scope and cost.

Existing pages remain public after a downgrade or cancellation unless explicitly unpublished; cancellation prevents authenticated edits. Unpublish a page before cancelling if you need to stop public access.

Control public access

To withdraw a client page, change its visibility to Private and save. Confirm its public URL no longer serves the page. Previously downloaded content cannot be recalled. Do not treat changing plans, renaming a client, or removing a report subscriber as revoking a status page.

For a legacy token link, the authenticated PATCH /v1/status-page endpoint accepts is_public: false to disable it or rotate_token: true to replace the token. Check the old URL afterward. This is separate from publishing or unpublishing a client page.

Explain what the status means

Use the page's displayed scope and timestamps when interpreting its headline. Availability, certificate, and DNS observations describe different conditions: a certificate warning does not by itself mean a website is unreachable. Review the affected components and incident detail rather than treating every critical alert as an outage.

Status pages and alert channels

A client status page is a shared public view. Workspace alert channels have a separate delivery scope: they receive severity-matching alerts across the workspace. Creating a client page does not make an email or Slack alert channel client-specific.

Next: read Alert Channels before configuring recipients, or Monthly Reports for the separate client-report workflow.