Audit log

See who changed what in your organisation and when, including every access by your agency or Plexivo support. Entries can never be edited.

The audit log is your organisation’s permanent record. It answers “who did this, and when?” for every change, whether it came from the console, the Plexivo CLI, an API key or Plexivo AI.

What is recorded#

  • Every change that succeeds: creating, changing and deleting resources, settings, members and keys.
  • Every refused change, when someone tries something their access does not allow.
  • Money, such as top-ups and charges, recorded together with the payment itself.
  • Access from outside your team: what your agency or Plexivo support viewed or revealed, and why. See Support and agency access.

Each entry records who acted, what they did, what it acted on, when, and the network it came from. Passwords, keys and other values you send are never stored in the log.

Find an event#

  1. Open the log. Go to Settings → Audit log. Recorded activity lists events newest first, with the Actor, Action, Target and When.
  2. Narrow it. Type in Filter by actor, action or target, or choose a period under When: the last 24 hours, 7, 30 or 90 days, or all time.
  3. Go further back. Choose Load older events.

The actor is a member’s email address, an API key by name, your agency, or Plexivo support. Every member of the organisation can read the log.

To read the log from a program, use GET /api/v1/tenants/{tenant_id}/activity. See Pagination.

Retention#

Entries are kept, unchanged. The database refuses any edit or deletion of an entry. They are stored in India.

For enterprises Use the audit log as evidence in access reviews and security questionnaires: it shows each change, who made it and every outside access.

Updated 27 October 2026