Activity log

The activity log records workspace-level changes: who joined, who left, which machine moved, when a plan changed. It is the sibling of the audit log — activity is admin-event-shaped, audit is request-shaped.

What is logged

The activity log captures:

Member invited, accepted, removed, role changed.
Machine added, removed, renamed, retagged, moved between workspaces.
Schedule created, edited, paused, resumed.
Billing events — plan change, seat change, payment method update, invoice issued.
Login from a new device or new country.
API token issued or revoked.

What is not logged here

This log deliberately does not include:

Individual command output — that lives in the Sessions inspector.
Agent-to-agent ask traces — those live in the desktop Activity tab.
Per-request audit — that is the Audit log.

Filtering and search

Filter by:

Actor — which member triggered the event.
Event type — invitations, billing, machines, schedules, tokens.
Date range — last hour to last 12 months (subject to retention).
Machine — narrow to events touching one machine.

Exporting

Export as CSV or JSON for external pipelines. The retention window depends on plan (typically 30–365 days). For longer retention, ship the events out via a webhook (workspace settings → integrations).

Compliance use

The activity log is append-only. Entries cannot be edited or deleted by Owners. Together with the request-level audit log it provides the trail that SOC 2 and ISO 27001 reviewers expect.

Where this data lives

Stored in the Django activity app and rendered by apps/my/.../dashboard/activity/.

Audit log — request-level events.
Workspace settings — retention policy.
Members