Skip to content
Audit logging

Activity trails for review and traceability.

Activity is designed to be captured as it happens, available when reviewers need it. Built to support audit work, not to be reconstructed under deadline pressure.

Evidence-grade intelligence · Human validation · Traceable decisions
Audit logging / evidence viewIllustrative view
captured activity trail
  1. Export preparedfinance lead · project scope
  2. Schema change appliedreviewer · dataset scope
  3. Join createdanalyst · workspace scope
  4. Source uploadedanalyst · workspace scope
  • CaptureAs work happens
  • AttributionUser, workspace, scope
  • TimestampsRecorded per event
  • ExportAvailable for review
The ReturnValue approach

Activity, designed to be captured as work happens.

You do not configure these to record; activity is captured as part of the platform itself. The steps below describe how the trail is built and used.

01

Capture

Core activity events (uploads, schema changes, joins, insights, reviews, exports) are captured as part of platform workflows, without a separate logging step.

02

Attribute

Events carry the user, the workspace, and the resource scope they affected. The trail says who, what, and where, alongside when.

03

Review

Reviewers read the trail alongside the work it describes, so an audit question can be answered without rebuilding the sequence by hand.

How the trail records

Events captured, attributed, and exportable.

Activity is designed to be captured as it happens, available when reviewers need it. It is built to support audit work, not to be reconstructed under deadline pressure. You do not configure these to record; activity is captured as part of the platform itself. A single workflow generates a sequence of events, each carrying a timestamp, the user who acted, and the resource affected.

Core activity events, including uploads, schema changes, joins, insights, reviews, and exports, are captured as part of platform workflows, without a separate logging step. Events carry the user, the workspace, and the resource scope they affected, so the trail says who, what, and where, alongside when. Time anchoring is built into how the trail is recorded.

A reviewer surface lets you scrub the trail by user, by document, or by time window, so the relevant slice is reachable in seconds rather than reconstructed by hand. Trails can be exported for hand-off to auditors or downstream systems, and exports preserve attribution, scope, and timestamps. Events stay linked to the artifacts they affected, so review can start from either side.

Capture
Core activity events are captured as part of platform workflows, without a separate logging step to wire up.
Attribute
Events carry the user, the workspace, and the resource scope they affected, alongside the timestamp.
Scope
Trail visibility is scoped to the workspace it belongs to; broader oversight requires explicit access grants, captured in the same trail as the events they reveal.
Retain
Retention controls are designed to align the trail with your compliance window. Specifics depend on the workspace, and we are happy to walk through what is configurable today.
Connected investigation

Events captured, attributed, and exportable.

A single workflow generates a sequence of events. Each event carries a timestamp, the user who took the action, and the resource it affected.

  1. 01ActWork performed
  2. 02CaptureEvent recorded
  3. 03AttributeActor and scope
  4. 04RetainTrail preserved
  5. 05ReviewQuestion answered
Evidence in context

Clarity at every decision point.

An audit trail is only useful if it was captured before anyone asked for it.

Illustrative view. Values shown are examples, not customer data.

Activity trail

Captured in workflow
  1. Source uploadedanalyst · workspace scope
  2. Schema change appliedreviewer · dataset scope
  3. Export preparedfinance lead · project scope
See ReturnValue in your environment

Follow your first financial signal.

Audit logging — Security | ReturnValue.ai