Insights
Insights in the workspace sidebar is a dashboard with a date-range picker. Its sections are tabs — Overview, Content, Localisation & media and Team — and both the range and the open tab are part of the page address, so a shared link shows the same view. A tab you never open asks for nothing.
Needs attention
The first tab leads with Needs attention: one line for each thing somebody can clear, with its count and what it is measured against. Click a line and a panel opens beside the page with the records behind it, the longest-waiting first, and a way out to the full list.
| Line | Counts | The panel leads to |
|---|---|---|
| Waiting to go live | Published records with edits nobody has published | The records list, per type |
| Waiting on review | Open review requests, and how many are overdue | Reviews |
| Gone quiet | Published records nobody has edited in over a year — the panel can also show 30–90 days and 3–12 months | The records list, per type |
| Images missing alt text | Images in the Media Library with no alt text | The Media Library |
The cards
| Tab | Card | Answers |
|---|---|---|
| Overview | Entries, Published, Drafts | Counts, and the change over the period |
| Overview | Media storage | Total bytes stored |
| Overview | Publishing velocity | Publishes over the range, and the busiest day |
| Overview | By type | Published, modified and draft records, per type |
| Content | Gone quiet | Published entries by time since last edit (≤30 days … over a year) |
| Content | Waiting to go live | Modified entries — published before, with saved edits not yet live |
| Localisation & media | Translation coverage | How far each language has got, by language or by type |
| Localisation & media | Storage | Storage by kind of file |
| Localisation & media | Uploads | Uploads over the range |
| Team | When the work happens | Edits by weekday and hour, in your time zone |
- You see a line or a card only if you may read its data (content:
content:read; media:media:read). - Each loads on its own. If one fails, it shows its own error — and a line that could not be counted shows no number rather than a zero. The rest of the dashboard keeps working.
The activity log
An audit trail of changes:
- Activity in the sidebar — the full log, for administrators.
- Each member’s page — their own activity.
- Home — recent activity, newest first and grouped by day.
- The entry editor’s History tab — the record’s own events between its versions, picked out by its Activity filter, for anyone who can read the record. (Until 0.12.0 it had a tab of its own; the old address opens History.)
What it records
The log is a table of When, Event and Workspace. The event is one sentence — Grace published Pricing FAQ — naming who (a person or an API token), what, and the item by its name. Click a row to open the event beside the table: the sentence, the exact time and where it came from, a Before / After table where the event recorded what changed, the actor, a link to the subject, the event ID, the raw metadata, and More by name to see what else that person did. Another row switches it; Esc closes it.
| Area | Examples |
|---|---|
| Sign-in and accounts | Signed in, failed sign-in, invited, role changed, reset link issued, invite link revealed, provisioned by SSO |
| API tokens | Created, used, revoked |
| Workspaces | Created, member added, content granted, archived |
| Content | Created, updated, published, unpublished, deleted, restored, purged |
| Review | Review requested, approved, rule changed, published without review |
| Media | Uploaded, updated, moved, deleted, folder created |
| Everything else | Saved views, segments and entry access, alarm rules, copilot skills and permission decisions, exports and imports, retried events |
A change and its log row are saved together — if the change happened, it is recorded.
Searching and filtering
- Search people, records, actions — one box matching the actor’s email, the item’s name, its id and type, and the kind of event.
- Time range — Today, Last 7 days (the default), Last 30 days, Last 90 days or All time.
- Filter — conditions on action, actor email, ID or type, subject type or ID, workspace and time, shown as chips you can remove.
The search, range and filters are part of the page address. Export CSV in the top bar downloads the current view — every page of it, up to 10,000 events; past that the file holds the newest and says so.
When an event could not be recorded
Rarely, an event fails to reach the log 15 times and stops retrying. When that happens:
- The Activity page shows a notice: how many actions were not recorded, and the most recent kinds. Home shows the same count as a card under Needs your attention — 3 actions not recorded — linking to the Activity page.
- Administrators see Review and retry — a list of the stuck events, each named as the log would name it, with when it happened, attempts, and the last error.
- Once the cause is fixed, click Retry on a row — it stays in the list marked Queued — or Retry all to retry the rows shown, one after another. Retrying twice is harmless.
Each retry is itself recorded as Retried a stuck event.
What it does not record
Only what a plugin reports is audited
The log records the events plugins report. A plugin your developers add that does not register its events is not audited — silently. The built-in plugins are all covered.
Reads are not recorded. Nothing logs that someone viewed a record.