Site activity
An audit log of who has done what across your site, used to investigate changes and meet compliance needs
Site activity is the audit log for supported user and system actions across your Basker site. Use it to answer "who changed this?" and investigate unexpected behaviour.
Open Settings → Site Activity. The screen is subtitled See the most important changes made across your site, including theme updates, sync activity, and other key admin actions. It has two sections: Filters and Timeline.
What's recorded
Each entry in the activity log includes:
- The action taken: create, update, delete, duplicate, publish, unpublish, restore, upload, and others.
- The module affected: pages, events, posts, themes, smart collections, blueprints, custom data, and so on.
- The actor: the user who performed the action.
- The resource: a reference to the specific record affected, with its title for readability.
- The time the action happened.
The log captures actions across most content types and operational areas. It's intentionally broad: anything that materially changes your site shows up.
Filtering and searching the log
The activity log can be filtered by:
- Time range: the last 24 hours, 7 days, 30 days, 90 days, or a custom range.
- Actor: actions by a specific user.
- Module: actions on a specific kind of content.
- Action type: only publishes, only deletes, and so on.
Combine filters to investigate scenarios such as every publish action on events in the last week or every delete by a specific user. Open an entry to see its resource title and any recorded context.
Common uses
- Investigating an unexpected change: "why is this page different?" → filter by resource, see the latest update, check who and when.
- Auditing publishes: see what's gone live in the last week or month.
- Reviewing a user's activity: for compliance, training, or hand-over.
- Spotting deletions: the activity log tells you what happened and when; whether the deleted content is recoverable depends on that content type and its retained versions.
The editor does not state a retention or export guarantee. Speak to Basker support before relying on the log for a formal retention or archival requirement.