Audit trail

CORA keeps a record of the work she does and the access decisions around it, so a team can see who asked for what, who approved it, and what actually happened.

Agent tasks and approvals

Every durable piece of work becomes a task. Each task records its origin, the executor that performs it, who requested it, who reviewed it and when, its status, its steps, and its result.

For a change to data or settings, the approval shows the exact proposed values, and the approval is bound to those values. When the task runs, CORA checks permissions and the old value again. If something changed after the preview, the task fails safely and asks for a fresh proposal instead of applying a stale change.

Where to look:

• More apps -> Inbox lists tasks by status, including those waiting for approval.
• Opening a task shows its live progress, decisions, and final result together.
• Tasks started from chat also appear as cards in the conversation.

Settings changes from chat

When you ask CORA to change a supported setting, such as the workspace name or your language, she creates a proposed task that shows the current and proposed value. Nothing is written until someone approves it, and the change is recorded like any other task.

Data use

On a file's detail page, the Data use card shows when CORA or an agent read the file, what left CORA, and where it was processed. Choose View audit trail to see the full history instead of only recent events.

Access and membership

• Settings -> People & access -> Company domains includes Domain access history: verification, configuration, join, removal, and restore events for your company domains. Owners and admins manage this section.
• Changes to company roles and permissions are recorded when they are saved.

What the audit trail does not show

Chats are private to the person who started them. Workspace owners and admins do not gain access to members' chats through the audit trail or any other setting.