GuidesAdmin
Audit log
Every meaningful change in the workspace, with who, when, what, and why.
The audit log is the workspace's running history of meaningful changes. Every project, sheet, item, attachment, share link, and member action is recorded with the user, timestamp, and (where applicable) the change reason.
Where to find it
- Workspace-level audit log, left nav → Audit (admin-accessible). Aggregates events across every project.
- Project-level audit log, open a project, then Activity in the project header. Filtered to that project.
What gets logged
| Action | Logged |
|---|---|
create | New projects, units, sheets, items, comments, share links, invites |
update | Edits to any field |
delete | Item, group, attachment, share link removals |
mark_complete / reopen | Sheet completion changes |
finalise / archive | Project status transitions to locked states |
convert_scope | Per-project ↔ per-unit conversions |
duplicate / copy_unit | Cloning operations |
revoke | Share links being deactivated |
| Member changes | Invites sent, accepted, revoked; role changes; removals |
Reading an entry
Each row shows:
- Who, the user.
- When, timestamp in your locale.
- What, action + target (e.g. updated item "Sink" on Plumbing / Master Bathroom).
- Diff, for
update, the from/to values of changed fields. - Reason, for any locked-edit (sheet completed or project finalised/archived), the change reason text.
Filters
The log supports filtering by:
- Date range
- User
- Action type
- Project (workspace-level log only)
What's not logged
- View events. Looking at a project doesn't generate a log entry.
- Catalogue browse. Adding/editing entries is logged; reading is not.
- Sign-in / sign-out. (Those live in a separate auth log accessible to the platform admin.)
Retention
Audit log entries are retained indefinitely. The log is append-only, entries can't be edited or deleted from the UI.
What admins should look at
- Reason quality, scan recent locked-edit reasons. If they're all "fix" or "update", the team norm needs work.
- Late-stage changes, many edits to a Finalised project may signal that finalisation happened too early.
- Member activity, quick sense of who's doing what; helpful when onboarding asks "is this person actually using the system?"