Jadiroon is used by five kinds of people, each with their own home screen and their own set of things they can do. This page is the map: who they are, where they land when they sign in, and which guide to hand them. If you only remember one thing, remember that the role decides the door — the same login URL sends each person to a different portal.
The five roles
Every login account is either staff, holding exactly one workspace role, or a portal account (employee, candidate, trainer). Access is enforced on the server for every page and action — the interface only ever shows you what your role allows. The table lists the main personas; staff roles are configurable per workspace (see Roles and permissions).
| Role | Who they are | Where they land | Their guide |
|---|---|---|---|
| HR Administrator (Workspace Admin role) | Owns the workspace. Configures everything, hires, assesses, and develops across the whole organisation. | /{slug}/app | HR Administrator guide |
| Line Manager (Line Manager role) | Runs a team. Same workspace app as HR, but people and development plans are scoped to their own reports, and with no Settings. | /{slug}/app | Line Manager guide |
Employee (EMPLOYEE) | A member of staff. Takes assessments, watches their competency profile, and co-owns their growth plan. | /{slug}/me | Employee guide |
Candidate (CANDIDATE) | An external job seeker. Applies to open roles and tracks their application. | /{slug}/candidate | Candidate guide |
Trainer (TRAINER) | A subject-matter expert applying to deliver training, through a separate hiring pipeline. | /{slug}/trainer | Trainer guide |
HR Administrator For HR administrators
The widest role. An HR admin sees the entire workspace: the hiring pipeline, every assessment, every person's competency profile and growth plan, the org chart and taxonomy, and the Settings area that no other role can open. Your workspace's first HR admin is invited when the workspace is created, and they can invite more. See the HR Administrator guide for the full walkthrough.
Line Manager For HR administrators
A line manager works in the same /app workspace as HR, but the platform narrows everything to their team — their direct and indirect reports, up to six levels down. They can assess their people, co-edit team growth plans, and move candidates through interviews they're assigned, but they cannot open Settings or author assessment templates. The Line Manager guide walks through exactly where the boundaries fall.
Employee For employees
An employee never sees the workspace admin. They have a personal portal at /{slug}/me for their own assessments, competency profile, career options, growth plan, and learning. The Employee guide is written entirely from their seat.
Candidate For everyone
A candidate is someone applying for a job. They browse the public job board, apply, and then track their application — assessments, interview slots, and stage progress — from the candidate portal. When they're hired, their Person record flips from candidate to employee. See the Candidate guide.
Trainer For everyone
A trainer is recruited through a separate pipeline from job candidates — for people who will deliver training rather than be hired into a role. They apply through the public training board and track their application in the trainer portal. The trainer pipeline has its own stages (including a Shortlisted stage). See the Trainer guide.
Personas that are really journeys
Some names you'll hear are not separate roles — they're one of the roles above, acting in a particular journey:
- Workspace Owner — the first HR administrator, invited when the workspace is created. They can't demote themselves unless another HR admin exists.
- Hiring Manager — an HR admin or line manager driving the Hire journey.
- Assessor — an HR admin or line manager administering assessments in the Develop journey.
- Growth Plan Collaborator — an HR admin, line manager, or employee co-editing a growth plan in the Grow journey.
Above the workspace: platform super admins
Platform super admins are not a workspace role. They belong to the Jadiroon deployment itself and work in the Platform Console, where they create workspaces and their first Workspace Admins and oversee every workspace on the deployment. When one of them enters your workspace, they act with the workspace role their console role names, and every visit shows in your Audit log.
Person vs role
Keep one more distinction in mind: a role lives on a login account, but a person is the talent record that moves through a lifecycle (candidate → employee → former employee) whether or not they can sign in. One person can map to a login in more than one workspace. The two are deliberately separate — see Person vs user.
Related reading
- Roles and permissions — the three workspace roles in full.
- Roles and permissions matrix — the surface-by-surface RBAC table.
- Account types and Available jobs — how candidate and trainer accounts work.
- The Hire → Develop → Grow arc — how the journeys connect.