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

# Activity and export

> Search and filter every verification and configuration change in your workspace, export it as CSV or JSON Lines, and pull it into your SIEM on a schedule through the audit API.

This page is for administrators, security teams and auditors who need to see what happened. When you finish you will know where to find a verification or a configuration change, how to export records, and how to feed them to your SIEM.

## Activity

Open **Activity** in the console. The **Trail** has two tabs:

* **Audit:** configuration changes, as actor, action, target and outcome: flows, factors, use cases, connectors, storage, the team and sign-in settings.
* **Events:** runtime activity. Verification requests are grouped into one row each (expand it to see every step: sent, opened, factors attempted, outcome), alongside console sign-ins.

![Activity page with Audit and Events tabs, Category, Outcome, Actor type and Channel filters, a search box, Export, and a table of actions with time, actor, target and outcome](https://mintcdn.com/truu-2/rMoRmNx6n3_l8xZg/images/idv/console-activity-light.png?fit=max\&auto=format\&n=rMoRmNx6n3_l8xZg\&q=85\&s=17a97196bbb5b5ba894e8e194023f806)

Filter by **Category**, **Outcome**, **Actor type** (Admin, User, Help desk agent, System, Anonymous, Setup script) and **Channel** (including **Self-service**), or search by name, email or ID.

Configuration changes record the before and after, so "who changed the SMS code expiry, when, and from what to what" has an answer.

> [!TIP]
>
> Failure patterns are signals. One person repeatedly failing Face on a help desk call is a risk picture. Many people failing one factor is usually a data problem: check coverage in [Connect your directory](https://docs.truu.ai/idv/connect/directory/overview.md#attribute-mapping-and-coverage), or E.164 formatting if the factor is SMS.

For trends rather than individual records, see [Insights](https://docs.truu.ai/idv/admin/insights.md).

## What records hold, and don't

Records hold outcomes and metadata, not verification content:

* One-time codes, knowledge answers and document images are never in the record.
* Contact details are masked. Where an event needs sensitive detail, it's held separately and referenced, with role-based access; each event says whether redaction applied.
* Face comparison happens at verification time; the record keeps the result, not biometric data.

See [Audit event reference](https://docs.truu.ai/idv/security/audit-events.md) for the event format.

## Export from the console

Choose **Export → CSV** or **Export → JSON Lines** on either tab. **Export → API for SIEM** copies the API endpoints for the pull described below. The export contains the records matching your current filters. Each export is itself recorded.

Audit records live in TruU's database, not in [your storage](https://docs.truu.ai/idv/connect/storage.md). Export them to keep a copy under your own retention.

## Send to your SIEM

TruU IDV doesn't push events to a SIEM. Instead, your scheduler pulls them from the audit API and forwards them. This works with any SIEM or log pipeline that accepts HTTP or files.

**1. Create an export-only API client**

In **Settings → API clients**, create a client with only the `idv:audit:export` scope (export includes read). Store its credentials in your scheduler's secret store, not in the script. See [API authentication](https://docs.truu.ai/idv/api/authentication.md).

**2. Pull on a schedule**

Every 5 to 15 minutes, request the window since your last successful pull, with a short overlap. Add `plane=control` for Audit only or `plane=data` for Events only; leave it out for both.

```bash theme={null}
curl -s "https://agent.truu.ai/api/v1/admin/audit/export?format=ndjson&occurred_after=2026-10-07T10:00:00Z&occurred_before=2026-10-07T10:15:00Z" \
  -H "Authorization: Bearer $TRUU_TOKEN" > truu-audit.ndjson
```

**3. Dedupe and forward**

Deduplicate on the event ID, then send the lines to your SIEM's HTTP collector or the object store your data lake reads. Give them their own source type, for example `truu:idv:audit`.

**4. Build detections**

Good starting points: repeated factor failures for one person; configuration changes to flows or use cases outside change windows; bursts of failed console sign-ins; connector credential rotations you didn't schedule.

The only push TruU makes today is verification status to a linked [ServiceNow](https://docs.truu.ai/idv/connect/servicenow.md) instance or [Microsoft Teams](https://docs.truu.ai/idv/connect/microsoft-teams.md) card.

## Retention

How far back you can search in the console depends on your agreement; contact TruU for yours. Exported data follows your own retention.

## Related

* [Audit event reference](https://docs.truu.ai/idv/security/audit-events.md)
* [API authentication](https://docs.truu.ai/idv/api/authentication.md)
* [Data handling](https://docs.truu.ai/idv/security/data-handling.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.