The Activity tab under Settings › User permissions is a searchable record of who changed access and settings, what they changed, and when. Use it to answer "when did this change, and who did it?" without guesswork, and as the audit trail your compliance reviews ask for.
Viewing Activity requires the Assign user roles capability — the same one that reveals the Users tab. This area is marked beta in the app.
What is recorded
Changes fall into two groups, and each is shown as a colored pill on the row.
Access changes
Category | Records |
|---|---|
Admin status | The elevated-access and active/inactive flags on an account |
Role membership | A person being added to or removed from a role |
Direct permission | A permission granted to or revoked from an account directly, outside any role |
Role | A role being created, renamed or deleted |
Capability | A capability being granted to or revoked from a role in the Permissions matrix |
In Admin status rows, elevated access is summarized as staff access or superuser access, for example "Granted staff access to …".
Settings changes
Category | Records |
|---|---|
Buffer rules | Edits to the buffer time added around exam durations |
Fiscal year | Changes to the fiscal calendar |
Annotation labels | Labels and label groups being created, renamed, recolored or deleted |
Colors | Edits to the Calendar color configuration |
Volume targets | Edits to the annual exam-volume goals |
Volume baselines | Edits to the Volume before Quantivly figures on Settings › Fiscal planning |
Settings changes are recorded by the app itself, so changes made directly in the database don't appear. Changes to Organization setup and to schedule annotations (operating hours, exceptions, reserved blocks and events) don't appear here either.
Opening a row also shows its source:
Source | Meaning |
|---|---|
API | Made in the Quantivly app |
Admin UI | Made by your Quantivly team, using the tools reserved to them |
System | Made by an automated process rather than by a person, such as a scheduled job or a step in a deployment. These have no actor and show as System |
Some changes only ever arrive as Admin UI or System, because they cannot be made in the app at all — granting an account elevated access is the clearest example.
Reading a row
Each row has five columns: When, Who, Action (the category and a one-line summary of what changed), Target, and Change. Open a row to see the full before-and-after for every field the change touched.
Where a change has no field-level difference to show — a role being created or deleted, for example — the row records the event without a before/after pair.
Times are shown in your deployment's timezone, not your computer's, so everyone reading the trail sees the same clock.
Filtering and searching
Filter | Narrows to |
|---|---|
All actors | Changes made by one person |
All targets | Changes made to one account |
All roles | Changes affecting one role |
All permission categories | One or more of the access categories above |
All settings categories | One or more of the settings categories above |
All time | Changes recorded between two points in time, counted in your deployment's timezone |
Search | Rows whose actor, target, role, capability or setting name matches your text |
The two category filters are separate dropdowns, so you can narrow to access changes and settings changes independently.
Deleted roles stay searchable: the trail records the role's name as it was at the time, so history does not go blank when a role is removed.
The trail is forward-only
Recording started when this feature was installed on your deployment. Changes made before that point were never recorded and are not retrievable — a banner above the list names the date the trail begins rather than implying nothing ever happened.
Access changes and settings changes started being recorded at different times, so the banner names a date for each rather than one date for the whole trail.
For the same reason, the very first recorded change to a given account or role may have no "before" value: there was no earlier record to compare it against.