VeloConnect — Guide

Audit log

The audit log is the answer to “who did what, when?”. Every user action and every system action that touches data writes a line to it. You’ll find it under Admin → Audit log.

What gets recorded

Pretty much everything that changes data or access:

  • Authentication — sign-in, sign-out, sign-in failure, with the IP address and user agent for each event.
  • Team changes — user invited, role changed, user suspended, user deleted.
  • Contacts — contact viewed, created, updated, deleted, exported. Custom contact field added, renamed, or removed.
  • Conversations — assigned, reassigned, closed, reopened, snoozed.
  • Campaigns — created, scheduled, launched, paused, cancelled.
  • Senders and templates — sender ID added, approved, or failed. WhatsApp template submitted to Meta, approved, or rejected.
  • DIDs — number requested, KYC approved, assigned to a user or channel, released.
  • Billing — wallet top-up, auto top-up trigger, refund issued.
  • Consent — channel opt-in / opt-out flipped on a contact (manually by an admin, or by the contact through a STOP keyword).
  • Pricing settings — rate or margin changes (admin-only, naturally).

What each entry shows

  • Timestamp — both UTC and your local timezone.
  • Actor — the user who did it, or system for automated events.
  • Action — a verb like contact.deleted, campaign.launched, did.released.
  • Target — the contact, conversation, setting, or other object the action touched.
  • Before / after values where a field changed — e.g. role change from agent to admin, or a sender ID status going from pending to approved.

Click any row to expand it for the full detail payload.

Filtering and exporting

The filter bar at the top of the log lets you narrow by:

  • Actor — a specific user, or just system.
  • Action type — pick from a tree (Auth, Contacts, Campaigns, etc.).
  • Target type — contact, conversation, DID, setting, and so on.
  • Date range.

The filtered view exports to CSV with one click. That’s the file you hand to an auditor, attach to an incident report, or keep in your own SIEM pipeline.

Retention

The audit log is kept indefinitely. Contact erasure (see Compliance) does not delete audit entries — the entry stays so you can prove the deletion happened, even though the deleted contact’s data is gone.

What’s not in here

Customer message bodies and call recordings are not in the audit log. Those live on each contact’s activity timeline and are subject to the data-rights workflows (export, erasure). The audit log is about actions on data, not the data itself.

Next