Skip to main content
AppendaHome
Sign inDownload

Table history

Review what changed on the table you have open. Table history is the right rail beside the grid — the same commit feed as Version control, filtered to one table.

Toolbar History opens the table history rail. Commits are scoped to the open table only.

Overview

Every meaningful change on a table writes one bounded commit: a CSV import, an enrichment batch, a new field, a view rename, and similar jobs. Table history lists those entries newest first without leaving the grid.

The workspace Version control tab shows the same feed across every table. Use table history when you are editing one dataset and want context beside the rows.

Open table history

  1. Open a table.
  2. In the toolbar right cluster, click History (clock icon — left of Run).
  3. The rail opens on the right with commits for this table only.
  4. Click History again or the rail close control to dismiss it.

The status bar can show the current table version short ref when a commit is selected.

What appears in the rail

Each row is one commit:

  • Past-tense title — for example "Imported 847 leads" or "540 leads were enriched"
  • Timestamp — absolute local time
  • Actor and channel — Local user on Desktop UI, agent-as-user, API, or MCP
  • Short ref — workspace-unique Crockford id from Rust (never invented in the client)

Enrichment commits show the provider logo and capability-style title. Schema adds and deletes use green or red accent strokes on the row.

Bulk work is one commit per approved job, not one commit per row or cell.

What gets recorded

Table history follows the same rules as Version control. Imports, enrichment runs, schema changes, and view create/rename/delete appear. Filter, sort, column width, show/hide, and freeze do not.

Tips

  • After Import, open history to confirm one summary commit for the whole file.
  • Click a table name in the workspace Version control feed to open that table with history already visible (when wired in product).
  • Restore and fork from a version are planned; history is read-only navigation for now.

Related

FAQs

Is table history different from Version control?
Same commits, different scope. Table history filters to the open table. The Version control tab shows workspace-wide activity.
Why is my filter change missing from history?
Filter and sort tweaks on the active view are not recorded in version history. They stay on the view.
Where does the short ref come from?
Rust persists a workspace-unique Crockford shortId on each commit. The UI renders that field only.
Does one cell edit create a commit?
Routine single-cell edits are normal table work. Bulk imports, enrichment batches, and similar jobs write one bounded commit per job.