> 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 Property Protect integration from staging to production, work
through the checks below with your AURA contact.

## Property Protect checklist

* **Credentials** - production credentials are stored server-side only and the
  production base URL is configured.
* **Fixed Location reconciliation** - every protected property resolves to one
  stable AURA `externalReferenceId`.
* **Bulk import** - if using CSV import, callback handling and post-import
  reconciliation have been tested.
* **Coverage and response types** - your system only exposes response options
  that are available for the relevant Fixed Locations.
* **Callout creation** - representative Fixed Location callouts have been tested
  end to end in staging. Use the **Responder Simulator** in the staging portal
  to drive callouts through dispatch, arrival, completion, and closure without
  AURA involvement.
* **Operator cancellation** - false alarm and no-response-needed flows cancel
  the AURA callout from your trusted backend.
* **Webhooks** - lifecycle events update your alarm, property, or operator
  system with idempotent handling. Verify these with the Responder Simulator,
  which emits each lifecycle webhook as you step a callout through.
* **Reports** - post-resolution reports are reviewed and downloaded in the AURA
  portal (not via the API), then stored or linked against the original alarm,
  property, or job record.