Audits and changelog

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.

Open Insights → Audit trail. The page header shows three counts: all events recorded, events today, and events in the last 7 days. Four cards below it show All events, Today, Updates and Deletions. These counts refresh about every 30 seconds.

Filter the audit trail

You can narrow the list with five filters:

Filter	What it matches
Event	One of 5 types: Created, Updated, Deleted, Restored or Action
Model	The kind of record changed, such as a subscriber or payment
Operator	The staff member who made the change
From / To	A date range
Search	Text in the URL, IP address, user-agent or model name

The list loads 50 rows at a time. Scroll down to load the next 50. Click a row to open its detail page with the old and new values.

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. Opening the page clears the dot. It comes back only when a newer entry is published. Your browser remembers what you have read for 1 year.

Each entry carries one of 5 labels: New feature, Bug fix, Improvement, Announcement or Release. Entries are listed newest first, 50 at a time. Each one has a share link to the same entry on the public Centipid changelog.

Changelog text explains product changes. It 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.