Audit Logs
Audit logs provide a chronological record of significant actions taken within your group. They help you answer the question: who did what, and when?
What Gets Logged
Vivreal automatically records audit entries for the following categories of actions:
Content Operations
- Collection CRUD — creating, updating, and deleting collections (schema changes, renaming, archiving)
- Object CRUD — creating, updating, and deleting collection objects (content entries)
- Media uploads — uploading, replacing, and deleting media files
Configuration Changes
- Integration changes — connecting, configuring, and disconnecting integrations (Stripe, social platforms, etc.)
- Site deployments — deploying, redeploying, and deleting sites
- Member changes — inviting, removing, and changing roles of team members
Each log entry captures the full context of the action so you can understand exactly what happened.
Audit Log Entry Fields
Every audit log entry contains the following information:
| Field | Description |
|---|---|
| Actor | The user who performed the action (name and email) |
| Action | What was done (e.g., collection.create, object.update, member.remove) |
| Target | The resource that was affected (collection name, object ID, member email, etc.) |
| Timestamp | When the action occurred (UTC) |
| Details | Additional context specific to the action (e.g., which fields were changed, old vs. new values) |
Viewing Audit Logs
Audit logs are accessible from the AuditPanel on the Group page. Only Owners and Admins can view them.
Navigate to the Group page from the sidebar.
Click on the Audit Log tab. The panel displays a chronological list of recent actions, newest first.
Use the filters at the top to narrow results by action type, actor, or date range.
Click on any log entry to expand it and see the full details, including what changed.
Audit Log Retention
How long audit logs are kept depends on your group's tier:
| Tier | Retention Period |
|---|---|
| Free | 7 days |
| Basic | 30 days |
| Pro | 90 days |
| Pro Plus | 365 days |
Audit logs older than your tier's retention period are automatically purged. If you need longer retention, consider upgrading your tier. There is currently no option to export audit logs, though this is planned for a future release.
Understanding Action Types
Audit log actions follow a consistent naming convention: resource.verb. Here are the most common actions you'll see:
collection.create— a new collection was createdcollection.update— a collection's schema or settings were changedcollection.delete— a collection was deletedobject.create— a new content object was addedobject.update— a content object was modifiedobject.delete— a content object was removedintegration.connect— a new integration was set upintegration.update— an integration's configuration was changedintegration.disconnect— an integration was removedmedia.upload— a file was uploadedmedia.delete— a file was removedmember.invite— a new member was invitedmember.remove— a member was removed from the groupmember.role_change— a member's role was updatedsite.deploy— a site deployment was triggeredsite.delete— a site was removed
Reliability Note
Audit logging uses a fire-and-forget pattern. This means that if the audit log write fails for any reason (network issue, database timeout), the original action still completes successfully. In rare cases, an action may not have a corresponding audit log entry.
Audit logs are best-effort. While the vast majority of actions are captured, do not rely on them as the sole source of truth for compliance-critical workflows.
Next Steps
- Roles & Permissions — understand who has access to what
- Usage Tracking — monitor resource consumption alongside audit activity