Activity
One log of what happened in the workspace, filtered by family. It is also where you audit what your agents did with the credentials you gave them.
What is recorded
| Family | Events |
|---|---|
| Docs | Document created, updated, deleted |
| Tasks | Task created, updated, completed |
| Messages | Channel created, message sent |
| Comments | Comment created |
| Agents | Agent connected, disconnected, and every credentialed provider call |
| Memory | Memory added |
| People | Member joined |
| Canvas | Canvas updated |
The filter tabs are narrowed to the families that actually appear in the log, and the tab you last used is remembered per workspace.
Auditing an agent's credentialed calls
Every call an agent makes through call_provider writes a row here, filed under Agents — because what a reader is auditing is which agent spent a provider credential, on what, and what came back.
A row records the provider, the operation, the HTTP method, the resolved URL, the response status and the duration.
It never records a request body, a response body, a header, or the name of the vault key used. Those fields are absent from the record's shape, not redacted from it.
Activity is not the audit log
The Activity window is a workspace feed. Some of its rows are client-authored events (a document edit, a task completion). That is the right design for a timeline and the wrong design for evidence of privileged actions.
Privileged actions — role changes, member removal, invites, permission-mode flips (including yolo), permanent tool grants, connect-token mints, vault writes — write a separate, server-authored audit log. Only managers can read it. The table is not on the generic database or realtime paths at all, so there is no client insert, update or subscribe door into the trail.
A row is always less sensitive than the thing it describes (key names, never values; token mints without the token). It is tamper-evident at the application layer, not tamper-proof against someone who holds the database credentials.
Commenting
Activity events can be commented on, so a question about something that happened stays attached to the thing that happened.