Audit log
The audit log records the significant actions of users and system events. It is opened from Settings → Audit log.
Who sees what
| Role | Scope |
|---|---|
| Super administrator | Entries of all companies and system events |
| Administrator | Entries of their own company only |
| Other roles | No access — the menu item is not shown |
The screen is not available with the Basic license or without a license; a Super administrator keeps access in that case as well. Entries are kept for one year and are then removed automatically.
The entry
| Column | Contents |
|---|---|
| Type | The event category |
| Action | The specific event |
| Who | The email address of the user who performed the action |
| From where | The client IP address |
| When | The date and time of the event |
| Where | The context of the event: the company, the project, or the name and version of the API used |
| What | The object the action was performed on |
| Before | The state of the object before the change |
| After | The state of the object after the change |
The Where, Before and After cells contain a multi-line list of parameters and their values. Entries are localized on display: the dates follow the format of your interface language and time intervals are shown in a readable form, for example "2h 5min 30sec".
Working with the list
- Filtering — each column has a filter opened by the magnifier icon in its header. Type and Action are selected from a dropdown of all known values, When uses a date range, and the remaining columns are searched by substring. Filters are combined with each other, applied with Search and cleared with Reset
- Sorting is not used: the log is always shown newest first
- Pagination — the log is split into pages; the page size can be changed
- Refresh reloads the log from the first page
- When nothing matches the filters, the list shows "No entries found in the audit log" together with the Clear search action
- The log cannot be exported from the interface
Event categories
| Category | What it records |
|---|---|
| User authentication | Successful and failed sign-ins, password reset requests |
| User management | Adding, editing and deleting users, activation, role and company changes, lockouts and their expiry |
| Company management | Creating, editing and deleting companies |
| Security settings | Enabling and disabling the IP lists, adding, editing, activating, excluding and deleting addresses |
| License management | Applying, changing and deleting a license |
| Project management | Creating, cloning, editing and deleting projects |
| Project access management | Granting, changing and revoking a user's project access, and project owner changes |
| Project version management | Creating, editing and deleting versions, marking a version global |
| RMD column configuration | Changes to RMD column settings |
| RMD element management | Adding, changing and deleting measures, dimensions, facts and relationships |
| Dimension group management | Adding, changing and deleting dimension groups |
| Fact table management | Operations on fact tables, the data model and their filters |
| Data mart management | Adding, changing and deleting data marts |
| Connection management | Creating, editing, activating, disabling and deleting database connections |
| Git | Creating, editing, deleting and testing Git connections, their use for export and import, and connection errors |
| Export | Project version export to a file or to Git, including failed exports |
| Import | Project version import from a file or from Git, including failed imports |
| API access | Successful and failed requests made with an API key |
Notes:
- Every public API operation, successful or failed, produces an API access entry with the caller's email address, the IP address, the time, the company, the name and version of the API used, the request details and the affected object
- A Super administrator sees API access entries for all companies; an Administrator sees them only for the users of their own company