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

# Use the Oriant dashboard

> Understand the Oriant dashboard, device evidence, directory coverage, and exports.

The dashboard turns Agent rollups and device evidence into an organization-wide
view of AI-tool use. The active organization determines which data you can see
and change.

## Overview

**Overview** summarizes the last 30 days of observed provider activity and shows:

* the providers with the most activity
* a decision queue for newly discovered providers that still need a sanction state
* policy review progress over the last 14 days
* reporting coverage for active directory users

Use **Add machines** to connect a single machine or open the fleet deployment
flow. Use **Export** to download an inventory or audit pack.

## Users

**Users** groups provider rollups by stamped identity. Expand a person to see
their providers, request counts, sanction states, blocked attempts, and recent
daily activity.

The **Coverage gaps** tab lists active SCIM users with no Oriant rollup in the
last 30 days. A coverage gap means Oriant has no recent proxy report for that
directory user; it does not prove that the user has not used AI tools.

## Assets and device evidence

**Assets** lists enrolled machines with their stamped identity, hostname,
enrollment date, last heartbeat, and device status:

| Status     | Meaning                                     |
| ---------- | ------------------------------------------- |
| **Active** | Heartbeat received within the last 4 hours. |
| **Silent** | Last heartbeat was 4 to 72 hours ago.       |
| **Stale**  | Last heartbeat was more than 72 hours ago.  |

Open an asset to review the latest device evidence snapshot. Evidence can show
installed AI agents, MCP server entries, and the names of AI credential
variables. Oriant does not collect the values of those credentials.

## Directory

**Directory** shows SCIM-synchronized users and groups. To connect an identity
provider:

1. Open **Settings → General**.
2. In **SCIM Provisioning**, generate a bearer token.
3. Copy the SCIM base URL and token into your identity provider.

The token is shown only when it is generated. Regenerating it immediately
invalidates the previous token.

## Exports

The **Export** menu is available from the dashboard header. Choose **Inventory
CSV** or **Audit pack (.zip)**, then export the last 7, 30, or 90 days, or all
time.

The audit pack contains:

* `ai-tools-inventory.csv` with providers, sanction state, reach, request volume,
  blocked count, and device-evidence indicators
* `endpoint-evidence.csv` with the latest device snapshots, detected AI agents,
  MCP servers, and credential variable names
* `README.txt` describing the files and the data-minimization boundary

## Organization settings

Settings also includes organization details, members, deployment, and API
credentials. **Collector Tokens** are organization-wide credentials used by
the Agent; each token is shown once and can be revoked. Regular integration API
key creation is not currently available in the dashboard.