Skip to main content
Audit logs record who did what, when, and to which record in your workspace. Use them for compliance reviews, troubleshooting, or to see what changed and when.

What’s tracked

Each event records:
  • Who performed the action
  • What they did, such as created, updated, deleted, restored, viewed, downloaded, exported, or changed who has access
  • Which record was affected
  • When it happened
  • Where it came from: the web app, the mobile app, glasses, Bower, a connector, or an external client
  • What changed: field-by-field before and after values
Tracked records include notes, attachments, protocols and their steps and versions, spreadsheets, collections, equipment, tags, and version snapshots. Workspace changes are tracked too: members, invitations, roles, sharing and access, connectors, and the subscription.

Viewing audit logs

Open Settings > Security, then Audit logs under History, or go directly to app.bowerlabs.ai/audit. You can also search for “Audit logs” in the command palette. Owners, admins, and members can open audit logs; guests can’t. You see events only for records you can open, so a private note’s events stay hidden from members who don’t have access to it. Each entry shows a readable description, for example “Jane Doe updated Note ‘Sample batch 14’.” Expand any entry to see the specific fields that changed, with before and after values. Times show in your device’s time zone. Hover over or tab to a time to see the zone’s name and the exact time in UTC.
Bulk operations performed within a few seconds are grouped together, with a count badge showing how many items were affected.

How far back you can see

Bower keeps audit events for 7 years (2,555 days) on every plan, and you can view, search and export all of them. Your plan doesn’t limit how far back you can look. Events older than that are deleted, except events about a signed record. Once a protocol run or collection has been signed, Bower keeps its audit events for as long as your workspace exists, however old they are. The same goes for everything that was inside it when it was signed, such as a collection’s notes, files and sub-collections or a run’s captures, and for the protocol a run followed. Withdrawing a signature or unlocking the record doesn’t change this. If the workspace is deleted, its events follow the 7-year limit again. The integrity check counts deleted events as expired, not as a break in the chain.

Integrity check

Bower seals each new event into a hash chain. Each sealed event’s hash covers its contents and the hash of the event before it, so editing, deleting, or reordering a sealed event breaks the chain. Bower checks every workspace’s chain once a day. The result shows under the page title:
  • Audit trail verified: every sealed event matched the chain at the last check.
  • Audit trail check failed: the last check found a mismatch, and Bower’s team has been alerted.
Beside the result is the time that check ran. Hover over or tab to it to see the exact time in UTC. A new workspace shows neither until its first check has run. When a person deletes their Bower account, the events they performed show Deleted user instead of them and lose their IP address and user agent. Events about the person lose their name, email, and change details. The events themselves stay, so the record of what was done remains, and the check still verifies everything that was not erased.

Filtering

Use the filter controls at the top of the page to narrow results:
  • Date range: presets for the last 7, 30, or 90 days, or custom start and end dates
  • Type: the kind of record, such as note, protocol, or collection
  • Action: what was done, such as created, deleted, or access granted
  • Created by: the workspace member who performed the action
  • Performed from: where the action came from, such as the web app, the mobile app, glasses, Bower, or an external client
  • Search: filter by record name or description
Filters combine, so you can find every note a specific member deleted from the mobile app in the last 30 days.

Exporting to CSV

Click Export CSV in the top right to download the current filtered view. The export respects the filters you have active, so narrow your view first if you only need a subset. The file is named audit-logs-{timestamp}.csv. Each row is one event, with these columns: An export holds up to 10,000 events. When your filters match more, the newest 10,000 are exported and a final row starting TRUNCATED: gives the date of the oldest event included. Narrow the date range to export the rest. A value that a spreadsheet could run as a formula is written with a leading ', so it shows as text instead. See Formula-safe CSV exports for exactly what changes and what it doesn’t cover.

What’s shown in change details

When you expand an audit log entry, you see exactly what changed:
  • Name, title: the record’s display name
  • Content: shows “Content was edited” (full diffs are not displayed for privacy)
  • Tags: added tags shown with a plus, removed tags shown with strikethrough
  • File metadata: file name, size, type, dimensions, duration
  • Parent collection: when a note is moved between collections
  • Processing status: when text extraction or transcription status changes