> ## Documentation Index
> Fetch the complete documentation index at: https://docs.operata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Assure

> Surface is the application layer — the dashboards, synthetic assurance, and account controls that put observations and insights in front of a person.

Surface is the application layer. It reads the observations and insights [Monitor](/docs/core-overview) produces and puts them in front of a person — never a raw signal.

## How it works

Three things sit on Surface.

* **Dashboards.** The Operata app renders contacts, agents, cohorts, logs, and the [insights](/docs/insights-overview) raised against them. The [User Guides](/docs/help/getting-started) cover every dashboard page by page.
* **Synthetics and assurance.** [Heartbeat](/docs/heartbeat-setup) places synthetic test calls into your contact center on a schedule, and the [Virtual Agent](/docs/virtual-agent) answers them, so you measure the path end to end without waiting for a real customer to hit the fault.
* **Account and access.** [Single sign-on](/docs/guides-request-sso), groups, and teammate permissions control who sees what.

## Why synthetics sit alongside dashboards

A dashboard tells you what happened on the contacts you had. A synthetic tells you what would happen on the next one. Running both on the same observation model means a Heartbeat result and a real contact are compared like for like — same fields, same insights, same thresholds — so a synthetic failure points at the same root cause a live contact would.

## Related

* [Insights overview](/docs/insights-overview) — what the dashboards raise and why.
* [Set up Heartbeat](/docs/heartbeat-setup) — the routing profile, contact flow, and number that drive synthetic calls.
* [User Guides](/docs/help/getting-started) — dashboard-by-dashboard help for end users.
* [Build](/docs/api-getting-started) — the same data over the API, for when a dashboard is not the destination.