Audit log and acting as someone
The platform audit log, its filters and export, and how impersonation for support works and is recorded.
The log is append-only: the app's database user can only add rows (since v0.2.0).
- Platform (Super → Audit log):
- filters: workspace slug, who (super admin, member, customer, system), action prefix, search (email, id, IP), date range, impersonation only;
- 50 entries per page;
- each entry has a page with a field-by-field before/after table;
- CSV export.
- Workspace (Settings → Audit log, owners):
- same filters, always bound to the workspace;
- entries made by super admins appear as Platform admin, without their email.
Start. On a workspace page:
- Act as next to a member;
- Find a customer → Act as next to a customer.
A reason (ticket number or note) is required and written to the workspace's audit log.
The session:
- uses the normal member or customer cookie, marked with the super admin's id;
- lasts at most 1 hour, with the usual idle limit;
- ends when the super admin signs out or is disabled;
- does not appear in the person's own device list.
While acting:
- A banner shows who you are acting as, with a Stop button. Stopping returns you to the workspace page in the super area.
- Every action is logged under the person, with
impersonator_idset to the super admin. - Blocked, because they would change the person's own sign-in:
- member password changes;
- signing out one session or every session;
- saving the customer profile;
- customer sign-out-everywhere.