The Audit log answers "who did what, to which record, and when" for your whole workspace. Every change anyone makes is written to it, along with sign-ins, data exports and every visit by a platform super admin. Nobody can edit or delete an entry, from the workspace or from the console.
Where to find it
Settings → Audit log (/{slug}/app/settings/audit-log). Roles holding Audit log view see it: the Workspace Admin and the seeded Viewer role, plus any role you give it to (see Roles and permissions). The page is read-only.
What is recorded
- Every change, in every module: creating, editing, deleting, moving a candidate to another stage, sending, importing, approving. For example Moved an application to another stage, Updated a job description, Updated a role or Changed a user's role.
- Employees' own changes from their portal: editing their profile (field names only, never the values), changing their photo and submitting a credential for review.
- Successful sign-ins, with the method: password, authenticator app, email code, or a trusted device.
- Data exports: people, job descriptions, org units, workload, gap analysis, participation and the audit log itself, with the filter used and the number of rows.
- Changes made with AI carry a via AI tag and the feature that made them. AI acts with the permissions of the person who asked it, so it can never do more than they can.
- Automatic changes, such as CV screening, automatic stage moves or an assessment being finalised, show as System · source.
- API integrations: changes made through a workspace API key show as Integration · name, with the key prefix in the details.
- Platform super admins: each visit to your workspace, the role they entered as, what they changed while inside, and what they changed on your workspace from the console.
Page views and other reads aren't recorded, and neither are attempts that failed validation.
Reading an entry
Each row shows when it happened, who did it, the action and the record, newest first, 50 per page. The record keeps its name even after the record itself is deleted, so the log stays readable.
Open a row to see:
- Changes: each field's value before and after.
- IP address and browser the action came from.
- Any extra details, such as the filter of an export or the permissions added to a role.
Passwords, tokens and secret keys are never stored. A candidate's email, phone and national ID are masked for viewers without See candidate contact details (see Candidate contact visibility).
Filtering
Filter by Person, Module, Action, Record type, Record ID, Actor type (choose API integration to see only what API keys did), and a From / To date range (whole days, Riyadh time). Apply runs the filter; Clear removes it.
Two tabs sit above the table:
- All events.
- Super admin activity: only what platform super admins did in or to your workspace. This replaces the earlier Platform access page; its old link opens this tab.
Exporting to CSV
Export CSV downloads every entry that matches the current filter, up to 50,000 rows, in a file that opens directly in Excel (Arabic included). It needs the named permission Export the audit log (CSV), which the Workspace Admin holds. The export is itself recorded, with its filter and row count.
History on a record
Job descriptions, job families, positions, a candidate's application (on their profile), training positions and trainer applications have a History panel: the same entries, limited to that record. View all in the Audit log opens the log filtered to it.
You see History when you can open the record and your role holds Audit log view.
Super admin visits
Super admins who operate your Jadiroon deployment can enter your workspace to help you. Inside, they work with the role their console role names (for example Talent Acquisition), never more, and a banner tells them so. Their account doesn't appear in your people or team lists and never counts as one of your Workspace Admins. Everything they do shows as Super admin their name.
A visit shows as an entry and an exit. An exit via Return to console or sign-out is recorded; a visit that ended because the session expired has no exit row.
Kept for good
Entries are append-only and kept for the life of the workspace. No page, API or role can change or remove them. The platform operator's console shows the same entries when filtered to your workspace.