This page covers features gated by Admin-tier permissions — typically Settings access. Admins have these by default; your administrator can adjust who has them in Settings > Team.
What’s logged
Each entry captures the event type, the user (or driver), the time, and a short message. Many entries also record the before and after values where a record was updated. The audit log covers actions such as:- Sign-in activity — successful logins, failed attempts, and blocked attempts.
- Support sessions — when Digital Florists support signs in or out of your shop.
- Customers — created, updated, merged, or deleted.
- Customer addresses and contacts — created, updated, or removed.
- Orders — cancellations, reopens, label prints, location changes, attachments.
- Transactions — voids and unvoids.
- Team — new team members and profile updates.
- Settings — changes to payment methods, locations, tax rates, delivery slots, occasions, banners, promotions, categories, and similar reference data.
- Data exports — when financial or end-of-day reports are exported.
Searching and filtering
The table sits on the Settings > Audit Logs page, with the most recent entries at the top. You can:- Search by event type, message text, username, driver name, IP address, or actor identifier.
- Filter by user, driver, event type (auth success, auth failed, auth blocked, data export), or outcome.
- Sort by ID or creation date.
Retention
Entries aren’t deleted on a schedule and the page is read-only — there’s no edit or delete control in the dashboard. If you need to share a slice with an external auditor, get in touch with support and they can help pull the records you need.Common questions
Can I see who looked at an order without changing it?
Can I see who looked at an order without changing it?
Read events aren’t logged. The audit log focuses on changes and sign-in activity, so the table stays readable.
Why can't I find a specific change in the log?
Why can't I find a specific change in the log?
Coverage varies by surface — some areas write detailed entries, others don’t write any. If you can’t find what you expected, get in touch with support with the order or record details and they can check.
What if a logged action looks suspicious?
What if a logged action looks suspicious?
Get in touch with support with the entry ID and a short description. They can pull the full context, including the request path, IP address, and the raw before/after values.
What’s next?
Team
Manage roles and permissions.
Disaster recovery
Restore data from an earlier point in time.