Skip to content
ChecktivChecktivChecktiv Docs

Activity log

View as MarkdownOpen in ChatGPT(opens in new tab)Open in Claude(opens in new tab)

The activity log records every privileged operator action against your organization: workflow template edits, webhook changes, API key issuance, and other configuration mutations. Each row is an append-only audit event with the actor, the action, and the resource it touched.

Open the activity log

Section titled “Open the activity log”

Open Activity while the right organization is active in the top-right switcher. The feed shows the most recent 50 events, newest first.

The activity log is restricted to Owner and Admin. Other roles see a notice and the feed is hidden. See Manage access for the role matrix.

What appears in the log

Section titled “What appears in the log”

Each row shows the event timestamp in your local time zone, who performed the action, the canonical action name (for example, kyc.template.created), the affected resource with a link where one exists, and a collapsible disclosure with the action metadata.

Action families currently surfaced:

  • Workflow templates — kyc.template.* (created, AI-generated, preview token issued).
  • Webhook subscriptions — kyc.webhook.* (created, updated, deleted, secret rotated).
  • Applicant verifications: kyc.session.* (created, canceled, note added, resend, refresh link, manual review, PDF exported, applicant PII viewed).
  • API keys — kyc.api_key.created, kyc.api_key.revoked.
  • Organization configuration — branding updates and related settings changes.
  • Identity-verification evidence and scans - kyc.idv.* and idv_image.* (an evidence image fetched through the API, and the refusals), and kyc.id_scan.* (the standalone ID-scan endpoint). These are written by an API key rather than by a teammate, so the row names the key instead of a person. See Evidence images.

Applicant-driven events appear with the system actor badge. The applicant’s identifier is never rendered.

Who the actor column names

Section titled “Who the actor column names”
  • A teammate: their name, with their email address in parentheses. If they later leave the organization, the row keeps its action and its resource but shows the neutral system badge in place of the name. The log never renders a raw internal identifier.
  • One of your API keys: an API key badge, then the key’s name and its display prefix, the same pair you see under Developers → API keys. Rows written through the API with one of your keys are labeled this way, so an action taken by one of your own credentials is not presented as an action taken by the platform.

A revoked key still resolves to its name and prefix. Revoking a key marks it revoked rather than removing it, which is what lets you answer “was this the credential we revoked?” long after the fact. To identify the key on a row, match the prefix it shows against the list under Developers → API keys. See Rotate or revoke an API key.

Drill into an event

Section titled “Drill into an event”

Click a row to expand it. The disclosure shows the structured metadata recorded with the event: a workflow template ID and change snapshot for an edit; a key prefix and the role that minted it for an API key issuance. Personal data is redacted at the source.

When the action targets a resource with its own console page, the row includes a link to it.

Filter by actor, action, or date

Section titled “Filter by actor, action, or date”

Use the filter dropdown to scope by action family. Choose All to clear the filter. The URL reflects the active filter so you can share a filtered view.

Pagination is cursor-based. Use Next page → to walk back through history and ← Previous page to step forward; both links preserve the current filter.

Export the log

Section titled “Export the log”

For exports, audits, or long-window analysis, use the public API with a key scoped to the right organization and mode. See API keys and Modes and regions.

Retention

Section titled “Retention”

Audit events are retained for the full data-retention window configured for your organization. Rows are append-only — they cannot be edited or deleted, and applicant identifiers are scrubbed when an applicant exercises their right to erasure. The retention window is configured under Compliance.

Section titled “Related”