The activity log

The Activity page is a workspace-wide timeline of who created, edited, deleted and restored what. It is the quickest way to answer “what happened here?” when a shared workspace surprises you.

Opening it

Choose Activity in the sidebar, or type “activity” (or “history”, “log”, “changes”) into the command palette. Each workspace has its own log, and the page shows the one you are in.

Everyone in the workspace can read it, whatever their role: owners, editors and viewers all see the same timeline. People outside the workspace cannot.

What it records

Content changes:

Saving a new model together with its fields shows as one “created a model” entry, not one entry per field.

Changes to the workspace and its people:

Things that belong to your account rather than to a workspace — signing in and out, changing your password — are not shown here.

Reading an entry

Each entry says who did it, what they did, what it happened to and when, newest first. The name of the document, model, field or feed links to it, and many entries show a short summary of it underneath — a document’s values, a model’s fields, a field’s type and options.

Two things worth knowing:

Changes made by a connected AI agent carry a via badge naming the agent’s key or app, so you can tell an agent’s edit from a person’s. The badge links to the Agents page — see Use Simplist with Claude, ChatGPT and other AI assistants. Changes the app makes on its own, such as emptying old items out of the trash, are attributed to “Someone”, as are entries left by a person who has since deleted their account.

Going further back

The page shows the most recent entries first; Load more at the bottom fetches older ones. Entries are kept indefinitely — nothing ages out of the log.

The log has no filters and cannot be exported. It is not included in workspace exports or backups.

The Activity page needs a connection: it is not saved for offline viewing.

Activity and version history

The two are related but answer different questions. The activity log is one timeline across the whole workspace: what happened, and who did it. Version history belongs to a single document, model or field and keeps the full content of every version: what did this look like before, and can I have that back. Restoring is done from version history, never from the log.