Activity log
# Activity log
The **Activity log** tab on a product shows the verifications that ran against its active configuration. It's read-only, fed live from your verification records.
It's empty until the configuration is deployed and traffic starts arriving. The log shows up to the most recent 200 verifications.
## What you see
Finished verifications, grouped into two collapsible sections, **Passed** and **Failed**. Pending verifications are not shown; only completed ones appear. A `valid` result lands in **Passed**; `invalid`, `error`, and `expired` land in **Failed**.
Each row shows, in order:
| Field | Meaning |
| --- | --- |
| Document | The document type from the verification's metadata (e.g. passport); shows `Document` when none is reported. |
| Security level | The assurance level of the document that was actually verified (Standard or High Security), derived from the presented document. |
| Time | When the verification finished. |
| Environment | `test` or `live`. |
| ID | The verification's identifier. |
Each row sits in a **Passed** or **Failed** section. Click a row to open a popover with the proof-request details.
## What you won't see
* Personal data the user did not disclose. If your flow asks for an age threshold, you see the pass or fail result, not the date of birth.
* The raw document or proof. Self verifies it; you never see the underlying scan.
## Getting more
* **Real-time:** subscribe to [webhooks](/docs/self-enterprise/dashboard/webhooks/) instead of watching the log.
* **Programmatic:** read a single verification with the SDK's [`sessions.get(...)`](/docs/self-enterprise/sdk/nodejs/).
* **Audit trail:** stream a tamper-evident record of activity to your own endpoint via **Settings → Audit** (configured with a destination URL and a shared secret; not available on the free plan).
The Activity log tab on a product shows the verifications that ran against its active configuration. It’s read-only, fed live from your verification records.
It’s empty until the configuration is deployed and traffic starts arriving. The log shows up to the most recent 200 verifications.
What you see
Finished verifications, grouped into two collapsible sections, Passed and Failed. Pending verifications are not shown; only completed ones appear. A valid result lands in Passed; invalid, error, and expired land in Failed.
Each row shows, in order:
| Field | Meaning |
|---|---|
| Document | The document type from the verification’s metadata (e.g. passport); shows Document when none is reported. |
| Security level | The assurance level of the document that was actually verified (Standard or High Security), derived from the presented document. |
| Time | When the verification finished. |
| Environment | test or live. |
| ID | The verification’s identifier. |
Each row sits in a Passed or Failed section. Click a row to open a popover with the proof-request details.
What you won’t see
- Personal data the user did not disclose. If your flow asks for an age threshold, you see the pass or fail result, not the date of birth.
- The raw document or proof. Self verifies it; you never see the underlying scan.
Getting more
- Real-time: subscribe to webhooks instead of watching the log.
- Programmatic: read a single verification with the SDK’s
sessions.get(...). - Audit trail: stream a tamper-evident record of activity to your own endpoint via Settings → Audit (configured with a destination URL and a shared secret; not available on the free plan).
Was this page helpful?
Thanks for your feedback!
