TattvaDocs
Trust & administration

Audit log

The record of security-relevant and structural actions in your workspace — who did what, and when.

The audit log records administrative and structural actions so you can trace a change back to a person and a moment.

Where to find it

Open Settings › Audit log, or go to /settings/audit.

Only workspace owners can open it. Anyone else sees Audit log access denied with their current role.

The screen

  • Audit log, with "Events scoped to" your workspace and "Showing the 50 most recent."
  • Filters: an action menu (All actions or one action), an Actor email… search, Apply and × Clear.
  • Table columns: When, Actor, Action, Target, Workspace, Detail. Detail shows the first two pieces of context, for example a file name and size.

The page shows the 50 most recent matching events. There is no paging and no export button on this screen.

What's recorded

Structural and security-relevant actions in your workspace, for example:

  • Access: auth.forbidden when someone is denied an action, and rbac.denied when someone without the role tries to decide in the Review queue of the Workspace Library.
  • Members: workspace.member.invite, workspace.member.role_change, PII clearance grants and revocations, workspace.delete.
  • Sources: uploads, with the file name and size.
  • Ontology: candidate decisions in the Review queue (ontology.candidate.decide), correction reviews (memory.correction.review, with the outcome, the reference and the note), answer-feedback triage in Maintain › Feedback (memory.correction.triage: status, whether the team note changed, cards made) and correction deletions (memory.correction.delete), conflict resolutions, column-meaning overrides, branch accepts, rejects and reverts.
  • Boards, foresight settings and reasoning runs you cancel.

Sign-ins, sign-outs (auth.login, auth.logout) and API key creation and revocation (api_key.create, api_key.revoke) are recorded too, but without a workspace, so they don't appear in an owner's view. Your platform operator can see them.

What's not recorded

  • Each question you ask and each answer. Those are kept in your conversation history (the Sessions drawer), not in the audit log.
  • Each query the agent runs against your data.
  • Tracker runs. Their history is on each tracker's History tab.

If you need every data read logged for compliance, talk to your platform operator before you rely on this log.

What each event holds

  • The time, the actor, the workspace and project.
  • The action and its target (type and ID).
  • Context for the action.
  • A hashed IP address (the raw IP is never stored) and the browser or client.

Retention

Events are kept indefinitely. There is no automatic clean-up. If you need a retention policy, ask your platform operator.

Tips

  • Skim the log now and then for unusual patterns, such as repeated auth.forbidden events from one person.
  • When you review a decision, pair the audit log (who changed what) with the conversation (what was asked and answered). The Sessions drawer lists each person's own sessions; a workspace owner or admin can pick anyone with sessions in that workspace's projects, and a superadmin can pick anyone. Anyone else opens another member's session from its link.
Audit log — Tattva Docs