Audit Log

The audit log records activity in your studio so you can see what changed and when. It's part of the Studio plan.

Equipment events

Gear edits (equipment.updated)

When a gear item is updated, the audit log records an equipment.updated event with a changes array. Each entry in the array shows the field name, the value before the edit, and the value after.

Only specific fields trigger this event. The following fields are tracked:

Edits to fields that are not in this list do not produce an equipment.updated event. Archiving or deleting an item produces its own distinct event (equipment.archived or equipment.bulk_archived) rather than an updated entry.

Room moves (equipment.room_changed)

When you move a gear item to a different room within the same studio, the audit log records an equipment.room_changed event. This is a dedicated event separate from equipment.updated — a room move always produces its own entry.

The entry records:

• the item's previous room (from_room)
• the destination room (to_room)
• the studio the item moved within (from_studio and to_studio — both the same for a same-studio move)

Moving an item to the room it is already in is a no-op: no update is written and no audit event is recorded.

Valuation fields and the audit log

The manual_value_as_of and agreed_value_as_of fields record when a valuation was set, not the value itself. The audit log tracks these date changes because updating the date changes the declared basis of the valuation — even when the numeric value stays the same.

These fields are not adequacy fields: changing a date does not alter the item's cascade-computed current value. Only fields that directly change the computed value are treated as adequacy fields.

Room events

Room lifecycle actions are recorded in the audit log. All room events appear in the Studio category.

Room created (room.created)

When a room is created, the audit log records a room.created event. The entry includes the new room's ID and name.

Room updated (room.updated)

When a room is renamed or its photos are changed, the audit log records a room.updated event. The entry always includes the room's ID and its new name. When the name changed, the entry also includes the old and new name as a diff. When the number of photos changed, the entry includes the old and new photo count.

Room deleted (room.deleted)

When a room is deleted, the audit log records a single room.deleted event. One entry is written per delete regardless of how many items were moved — the entry summarises the whole reassignment rather than logging one event per item.

The entry includes:

• the deleted room's ID and name
• how many items were reassigned (reassigned)
• the destination room and studio the items were moved to (null when the room had no gear)
• whether the reassignment was cross-studio (cross_studio)

Import events

When a CSV or AudioDope import completes, the audit log records one import batch entry summarising the run. The entry shows:

• who ran the import
• which importer was used (CSV or AudioDope)
• the filename
• how many rows were in the file, how many succeeded, and how many failed

One entry is written per import, regardless of how many items were imported. The entry appears even when some rows failed — the counts tell you what landed and what didn't.

The entry is written on a best-effort basis. If the audit write fails, the import result is not affected — your items are still imported.

Import batch events appear in the Studio section of the audit log alongside equipment and maintenance events.

Audit log behavior

All room and equipment room-move audit writes are best-effort. If the audit write fails, the room operation or item move still completes — the user's action is never blocked by an audit failure.

Download CSV

When the log has loaded and contains at least one entry, a Download CSV button is available. Selecting it downloads all currently loaded entries as a CSV file.

The button is not shown while the log is loading or when no entries match the current filters.