Audit log — who changed what, and when
The audit log is the studio’s memory of what changed. Whenever someone on the team edits a setting, a client record, or your brand details, the studio writes a short entry: who did it, what they changed, and when. It’s the place you go when something looks different and you want to know how it got that way — no guessing, no group chat.
What it records
Each entry captures the person, the time, the thing that changed, and the kind of change — created, edited, or removed. For edits, it notes which details moved, so you see exactly what’s different rather than just “something changed”.
Routine, high-volume activity — like every post you draft or every image you generate — isn’t logged here; those would bury the signal. The log stays focused on the meaningful changes worth tracing. Entries are kept for a while and then cleared automatically, so the record doesn’t grow forever and old activity doesn’t linger.
How to read it
Open the log and you get a list, newest first. Filter by person to see one teammate’s activity, or search to jump to a specific change. Combine the two when you’re chasing something specific — “what did the new team member change last week” is a person filter and a glance.
Worked example
A client’s notes look wrong — a sensitivity you’re sure was recorded is gone. You open the audit log, filter to that client, and see one entry from two days ago: a teammate edited the notes during a busy afternoon and trimmed the wrong line. A thirty-second look settles it, and you restore the note. No one had to remember; the log did.