Activity and History

A persistent record of every change to a diagram, who made it, and the ability to revert any single one.

Every diagram keeps a running record of the changes made to it: who did what, and when. It is surfaced in the editor as the Activity Panel, and it lets you revert any single change on its own without disturbing everyone else's work. The log is saved with the diagram, so it survives reloads, sign-out, and re-sharing.

A change at a time

The unit of history is one change: a single undoable commit, such as adding a shape, picking a colour, or dragging a box. A change can touch several elements at once (a multi-select drag is still one change), and a continuous gesture like a drag or a held arrow key coalesces into one entry rather than one per frame. Each change becomes one entry in the log, recording which elements were affected and their before and after states.

Author details are frozen at the moment of the change, so renaming yourself later does not rewrite past history.

Two ways to step back

There are two complementary ways to walk back changes, and they stay in sync:

  • Undo and Redo live in the Activity Panel's header. Undo removes the most recent entry from the panel and the record; Redo puts it back exactly as it was.
  • Revert is a per-entry action: it cancels one specific change wherever it sits in the list, leaving everything that came after it untouched. This is the difference that matters in collaboration, reverting your typo from ten edits ago does not throw away a teammate's later work.

Read more in Reverting Changes.

Seeing the history

The Activity Panel is a floating panel, like the Explorer and Palette, that you can move around and minimise to a dock button. It is scoped to the active tab: it shows the entries for the tab you are looking at and swaps when you switch tabs. Each row shows the author's coloured dot, their name, a short summary ("Edited 'API'"), a relative timestamp, and a Revert button on hover. For more detail, see The Activity Panel.

Because new entries (and their removals) propagate through the same realtime channel as edits, collaborators watch each other's changes land in the panel in real time.

The panel lists the most recent entries, newest first. The full history is kept with the diagram, so the panel always reflects the latest activity even after a reload.

Was this article helpful?