Account administration
Audit log
A record of who changed the shop. It answers “who turned that off?” and “when did this setting change?” without anybody having to remember.
Where to find it
Account settingsAudit log.
Needs the permission audit_entries.view (view audit entries). Owners and Admins have every permission by default.
What is recorded
Administrative changes — changes to the business — rather than the day’s counter work. Currently 74 kinds of event:
- Account address changed
- Account closure scheduled
- Account suspended
- Account unsuspended
- Add-on added
- Add-on changed
- Add-on removed
- API key created
- API key revoked
- Billing details updated
- Blocked number’s locations changed
- Business name changed
- Customer data erased
- Customer data exported
- Customer messages resumed
- Customer opted out of messages
- Invitation resent
- Invitation sent
- Invitation withdrawn
- Joined the team
- Kiosk pairing code issued
- Kiosk tablet added
- Kiosk tablet paired
- Kiosk tablet removed
- Kiosk tablet renamed
- Location created
- Location deleted
- Location updated
- Locations and services added from website
- Marketing campaign sent
- Member location access changed
- Member role changed
- Member status changed
- Member’s email address changed
- Messages paused
- Messages resumed
- Number blocked
- Number unblocked
- Overage balance adjusted
- Overage charge marked failed
- Overage charged
- Overage settings changed
- Payment method removed
- Payment method updated
- Plan changed
- Plan limits adjusted
- Plan limits adjustment removed
- QR code created
- QR code design changed
- QR code removed
- Queue archived
- Queue created
- Queue updated
- Role created
- Role permissions changed
- Second trial refused, billed at once
- Settings changed
- Signed out everywhere
- Subscription cancellation withdrawn
- Subscription cancelled
- Subscription changed
- Subscription re-synced from Paddle
- Survey created
- Survey deleted
- Survey response deleted
- Survey updated
- Test number added
- Test number removed
- Trial ended early, plan started
- Trial started
- Waitlist cleared
- Webhook endpoint added
- Webhook endpoint disabled
- Webhook endpoint removed
What is deliberately not recorded
Calling, serving and no-showing customers are not in here, and that is on purpose. A busy shop generates hundreds of those a day, and burying the handful of entries that matter under a day’s counter work would make the log unreadable — a log nobody can read is not traceability.
Those movements are recorded anyway, in the places you would actually look for them: each visit carries its own timestamps, and every message sent is in the message log.
Queue changes means changes to the queues
Creating, renaming, archiving and reordering a queue are administrative changes and are logged. Moving a customer through one is not.
Reading an entry
Each row names who did it, what they did, when, and a short summary — “role changed from Editor to Admin” rather than a dump of the whole record before and after.
That is deliberate on two counts. It is what somebody reading the log actually needs, and copying a settings blob into the log would put customer and billing data in a second place with a second retention story.
Changes Queue Join support makes to your account are logged too. They show Queue Join support as who did it, with a one-line summary of what was changed. Entries the system makes on its own, with nobody behind them, show System.
When it earns its keep
- Something changed and nobody remembers changing it — usually a setting, usually last week.
- Somebody’s access looks wrong, and you want to know when it was granted and by whom.
- A customer’s data was exported or erased and you need to show when, and on whose authority.
- Working out why a marketing campaign went out, and who sent it.
Retention
Entries are kept indefinitely today; there is no automatic clear-out. They are removed when the account is deleted.