Shared Incident URLs

Every assembled incident has a shared URL. This URL is publicly accessible without authentication.

What the URL provides

The shared URL gives anyone who has it access to the full incident artifact: the causal chain, completeness label, first confirmed break, affected services, and the step-through timeline. The view is identical to what authenticated users see in the dashboard.

Access model

• No login required: the URL contains a unique token that serves as the access credential. Anyone with the URL can view the incident.
• No expiry on the URL: the URL remains valid for as long as the incident data is within your plan's retention window. After the retention period, the incident data is no longer accessible, but the URL itself does not become invalid — it returns a "not found" response.
• No write access: the shared URL is read-only. Annotations and comments require authentication.

What to do with it

Drop the URL into your war room thread, Slack channel, PagerDuty incident notes, or anywhere your team coordinates during an incident. Engineers who receive the URL do not need an Incidentary account to read the artifact.

When Incidentary sends a Slack notification, the URL is included in the message body. When PagerDuty or OpsGenie integrations are connected, the URL appears in the incident notes.

What the URL does not expose

The shared URL shows the assembled artifact — event types, statuses, durations, service names, and the causal chain. It does not expose:

• Raw request or response bodies (payload capture is disabled by default; even when enabled, it requires authentication to view)
• Internal system configuration
• Other workspaces' data