> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.aurasos.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.aurasos.com/_mcp/server.

# Go-live

Before moving your People Protect integration from staging to production, work
through the checks below with your AURA contact.

## People Protect checklist

* **Credentials** - production credentials are stored server-side only and the
  production base URL is configured.
* **Customer registration** - customer creation or hosted signup has been tested
  with representative users.
* **Subscriptions** - active, cancelled, and lapsed entitlement states are
  handled correctly before live panic actions are shown.
* **Panic UX** - the panic action follows the "Help in 2 Clicks" pattern and is
  available in the states your product supports.
* **Location handling** - GPS permissions, stale locations, low accuracy, and
  missing coordinates have defined behaviour.
* **Callout flow** - live-location callout creation, location updates,
  cancellation, and callout tracking have been tested in staging. Use the
  **Responder Simulator** in the staging portal to drive callouts through
  dispatch, arrival, completion, and closure (including the cancel and
  redistribute flows) without AURA involvement.
* **Webhooks** - lifecycle events are received, authenticated, de-duplicated,
  and mapped to your product state. Verify these with the Responder Simulator,
  which emits each lifecycle webhook as you step a callout through.
* **Reports** - your team knows that post-incident resolution reports are
  reviewed and downloaded in the AURA portal (not via the API).
* **Support process** - your team knows how to find the AURA `customerId`,
  subscription, and callout `id` for support requests.