Ceum keeps history in three different places. Each captures a different kind of change, and together they answer the question "who or what changed this, and when?"
The three places
1. Per-item changelog
For clients, projects, tasks, and invoices, every meaningful field change is recorded along with its before and after values and who made it. See Entity changelog.
- Where to find it — open an item and use its Changelog action.
- What's recorded — only the fields that actually changed, with their old and new values.
- Who made the change — either you (through the app) or an external tool acting on your behalf with a token.
- How long it's kept — indefinitely. It's removed if you delete the item itself.
2. Document version history
For documents, every time you save new content, the previous content is archived as a version. Edits to just the name, tags, or links don't create a version. See Document versioning.
- Where to find it — open a document and view its history.
- What's recorded — the full content of every earlier version, not a field-by-field diff.
- Who made the change — not recorded; versions capture content only.
- How long it's kept — indefinitely, and you can restore an earlier version without losing the current one.
3. MCP events log for external tools
Every change made by an external tool connected through Ceum's MCP tokens is recorded here. See Sessions and MCP events.
- Where to find it — the MCP events page.
- What's recorded — which tool acted, which token it used, which item it affected, and the details it sent.
- Who made the change — always an external tool acting on your behalf, identified by its token name. Tokens are managed under Integrations and MCP.
- How long it's kept — indefinitely. Read-only actions aren't recorded.
Which one to check
- "What did I do to this client last week?" — open the client's changelog.
- "What did this document say before I rewrote it?" — open the document's history.
- "What did my connected tool change?" — filter the MCP events log by the token name.
- "Who made this specific edit?" — start with the per-item changelog; it tells you whether it was you or an external tool, so you know whether to dig into the MCP events log.
Tips and edge cases
- Transactions, subscriptions, time entries, and quick list items have no per-item changelog. Their edits aren't tracked in any of these three places. If you need a firm record for those, export them periodically.
- Bulk edits produce one entry per item, not a single combined event.
- Token names stick around after you revoke them. Older MCP events entries still show the original token name.
- Document versions don't say who wrote them. If you need authorship for documents, record it elsewhere.