The changelog is a per-entity audit trail. Every meaningful field change to a client, project, task, or invoice produces an entry with before/after values and the actor who made the change.
Where it lives
Each client, project, task, and invoice has its own changelog. Open it from the entity's detail page using the Changelog or History action. Documents don't use this system — their history lives in Document versioning instead.
What gets recorded
Each entry includes:
- Timestamp — when the change was applied.
- Actor — either you (shown by your display name) or an MCP token (shown by the token's name). Each entry is labeled so you can tell them apart at a glance.
- Changes — the fields that changed, with their before and after values.
Housekeeping fields are left out of the diff, and only fields whose value actually changed appear in an entry — unchanged fields aren't shown as noise.
Field values are shown in a readable way:
- Dates use your configured date/time format from General settings.
- Currency fields use the symbol and precision from the same place.
- Status and similar values are title-cased.
- Yes/no values render as Yes / No.
- Lists render as comma-separated values.
Page layout
The changelog is a paginated table:
- When — the formatted timestamp.
- Actor — the name plus a small "user" or "mcp" badge.
- Changes — an expandable per-field before → after diff.
You can sort newest-first (the default) or oldest-first. There's no filter for actor, field, or date range — every change is shown, paginated.
Workflows
Find what changed today
Open the changelog and scan the top. Entries default to newest first; the actor column tells you whether the edits were yours or came from an MCP token.
Investigate a change made through an integration
Look for the "mcp" actor badge. Then cross-reference the MCP audit log under Integrations and MCP to find the tool call, scope, and originating client that produced the change.
Retention and permissions
- Kept forever. Entries aren't auto-pruned and don't expire.
- Read-only. Individual entries can't be edited or deleted.
- Removed with the entity. Deleting the parent client, project, task, or invoice also removes its changelog.
- Yours only. You can only see the changelog for entities you own.
Tips and edge cases
- Bulk edits split into per-entity entries. A single bulk-edit run on five tasks produces five changelog entries, one per task — not a single grouped event.
- Comments and time entries don't land here. Comments live on the task itself; time entries are separate. Both have their own history surfaces.
- Integration token names survive revocation. If you revoke a token, its past changelog entries still show its old name rather than going blank.
- Document changes don't appear. Use Document versioning for those.
On mobile
Not available on the mobile app — manage from the web app.