Skip to main content

​
Review operational history

Audit records and the changelog answer different questions:
  • Audits: who/what changed data in this workspace or performed a recorded action.
  • What’s new / Changelog: product updates published to operators.

​
Audits

The audit list/detail pages can show actor, action/event, affected model/record, time, old/new values, and request/context metadata where captured. Access is permission-gated. Use audits to investigate:
  • subscriber status/profile changes;
  • settings updates;
  • login/denied activity where recorded;
  • payment/invoice/expense changes;
  • staff/role actions;
  • destructive or bulk operations.
An absent audit row does not prove an event never happened; not every external provider/router action produces the same application audit. Correlate with domain records, provider references, router logs, and timestamps.

​
Changelog

The sidebar can show an unread indicator for a newly published entry. Open What’s new to read operator-facing releases. Changelog text explains product changes but is not a transaction/audit record and does not override current UI behavior.

​
Investigation workflow

  1. Record exact time/timezone, user, ISP, and affected record ID.
  2. Open the record’s own activity/history.
  3. Search audits around the time.
  4. Compare old/new values and actor/context.
  5. Correlate with provider/router/message status where relevant.
  6. Preserve evidence before corrective action.
  7. Avoid placing secrets or unnecessary personal data in investigation notes.