CloudM Continuity maintains a comprehensive audit log that records all significant events across your tenant. The audit log provides visibility into sync operations, administrative actions, and authentication events for operational monitoring and compliance purposes.
Accessing audit logs
- Click Logs in the sidebar
All roles (Super Admin, Admin, and Viewer) can view the audit logs.
What is logged
The audit log captures events from across the system, grouped into the following categories:
| Category | Events | Actor |
|---|---|---|
| Sync events | Sync started, Sync completed, Sync failed | System |
| Policy events | Policy created, Policy updated, Policy deleted | Admin user (email shown) |
| User events | User invited, User created | Admin user (email shown) |
| Authentication events | Logged in, Logged out | The user who signed in or out (email shown) |
Log table columns
Each audit log entry is displayed in a table with the following columns:
| Column | Description |
|---|---|
| Actor | Who triggered the event — either an admin user's email address (shown with a person icon) or "System" (shown with a system icon) for automated events |
| Severity | The severity level of the event: Information, Warning, or Error (see below) |
| Event | What happened (e.g. "Sync completed", "Policy updated") |
| Message | A description of what happened, including relevant context such as user emails, policy names, or error details |
| Timestamp | When the event occurred |
Severity levels
Each event is assigned a severity level, displayed as a colour-coded badge:
| Severity | Meaning | Examples |
|---|---|---|
| Information | Normal, successful operations | Sync completed, Policy created, Logged in |
| Warning | Something that may need attention but is not a failure | A sync that completed with skipped items |
| Error | A failure that requires investigation | Sync failed, sync failed to start |
Error-severity events are highlighted with a red background in the log table for visual distinction.
Actor types
The Actor column distinguishes between two types of actor:
| Actor | Icon | Description | Examples |
|---|---|---|---|
| User email | Person icon | Events triggered by an administrator or user action in the UI | Policy created, User invited, Logged in |
| System | System icon (dark background) | Automated events generated by the sync engine | Sync started, Sync completed, Sync failed |
Both types are shown in the same log view. You can filter by actor to find events triggered by a specific user.
Using audit logs for troubleshooting
The audit log is one of the first places to check when something unexpected happens:
- Sync failures — filter for "Sync failed" events to see error details and which users are affected
- Unexpected behaviour changes — check for recent "Policy updated" or "Policy deleted" events that may explain a change
- Tracking who made a change — use the Actor filter to find all actions performed by a specific admin
- Security review — filter for "Logged in" and "Logged out" events to review authentication activity
Compliance and auditing
The audit log supports compliance requirements such as DORA and NIS2 by providing a complete record of all operations and administrative actions within your tenant. You can export logs to CSV for reporting purposes.