On this page
The audit log is the append-only record of who did what in your VGraple CRM workspace: sends, broadcasts, template and flow changes, contact edits, member and role changes, settings updates and exports, each with the actor, the time and the IP address. It answers the questions that come up during an incident or an audit, and it records support actions by VGraple staff against your organisation as well.
Audit log
- 1Open Audit Log from the sidebar (on
- 2Use the date range and the action
- 3Click an entry to see the details
- 4Look for the super admin flag on
- 5Export the filtered list when you need
Before you start
- You need the audit view permission: Owner, Admin, or a custom role with it.
- Entries are recorded from the moment the workspace was created; there is nothing to enable.
Steps
- Open Audit Log from the sidebar (on the Android app: More, then Audit trail).
- Use the date range and the action filter to narrow the list, for example to broadcast sends in the last week or member role changes this month.
- Click an entry to see the details: the actor, their role at the time, the object (contact, conversation, template, flow, member or setting), the IP address and a summary of the change.
- Look for the super admin flag on entries performed by VGraple support inside your organisation.
- Export the filtered list when you need a copy outside the app.
What is recorded
| Area | Actions |
|---|---|
| Contacts | Create, update, delete, block, merge |
| Conversations | Start, resolve, reopen, assign, snooze |
| Messages | Send free-form, send template, send media, send CTA URL |
| Broadcasts | Create, send, retry, cancel, clone, retarget, delete, export |
| Flows | Create, delete, toggle on or off |
| Templates | Create, update, delete, clone, translate, appeal, toggle, bulk submit from the gallery |
| Members | Invite, role change, remove, profile edit |
| Settings | Organisation settings update, Meta Conversion Tracking update, Payment Collection update |
| Exports | Leads export, email export |
Reading an entry
Each entry shows the action name, the actor's name and email, whether the actor was a platform super admin, the target object with a link where it still exists, the IP address and the timestamp in your workspace time zone. For settings changes, the entry summarises which fields changed without revealing secret values.
Settings and options
| Setting | What it does | Default |
|---|---|---|
| Date range | Limits the list to a period | Last 30 days |
| Action filter | Shows one action type | All |
| Actor filter | Shows one member's actions | All |
| Export | Downloads the filtered list | On demand |
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Audit Log is missing from the sidebar | Your role lacks audit view | Ask an Owner or Admin |
| An entry shows a super admin as the actor | VGraple support acted in your organisation, usually during a support thread you opened | Check the support thread; contact support if unexpected |
| A deleted member's actions still show | Entries are never removed | Expected |
| Cannot find a message read | Reads are not logged | Use roles and teams to control visibility instead |
What the log does not contain
Message content is not copied into the log; the entry links to the conversation instead, so reading a customer's words still requires the role and team scope to open it. Views and searches are not logged. Sign-ins are visible under organisation sessions rather than here, and Meta-side events (template approvals, quality changes) appear on the template and channel pages, not in the audit log. Automated actions taken by flows, sequences and rules are attributed to the automation rather than to a person, which is how you tell a bot's send from an agent's.
Who should read it and how often
Owners and admins should scan the log weekly at first and monthly once the team has settled: a quick pass filtered to broadcasts, exports and member changes takes five minutes and catches the things that matter. Supervisors do not need it for daily work because the inbox itself shows who replied to what. Auditors and clients of an agency can be given the export rather than a login.
Reading it on the Android app
Under More, then Audit trail, the same entries are listed newest first with the same filters, useful for a quick "who sent that" check away from the desk. Export is web-only.
Common questions the log answers
| Question | Filter | What to read |
|---|---|---|
| Who sent that broadcast to the whole list? | Action: broadcast.send | Actor, audience size, template |
| Who changed the template wording before it was rejected? | Action: template.update | Actor and the before and after summary |
| Who exported the contact list last month? | Actions: export.leads, export.emails, broadcast.export | Actor, time, filter used |
| Who gave this person Admin? | Action: member.role_change | Actor, target member, old and new role |
| Did anyone from VGraple act in our account? | Super admin flag | The linked support thread |
| Who turned the payment gateway on? | Action: settings.payments.update | Actor and time (values are never shown) |
Retention and export
Entries are kept for the retention period stated in the DPA and are included in the data export you can request when leaving. Export the log monthly if your own policy needs a longer record; the CSV includes every column shown on screen.
Using the log during an incident
Start from the time the problem was noticed and work backwards: a broadcast that went to the wrong list shows the sender and the audience; a template that changed unexpectedly shows who edited it; a contact export shows who downloaded what. Combine the log with organisation sessions to see where the actor was signed in from, and with the roles reference to tighten permissions afterwards.