Jadiroon's taxonomy is the chain Sector → Sub-sector → Job family → Job description → Position → Competency. The top of that chain — sectors, sub-sectors, job families and competencies — is a global library shared by every workspace. Each workspace picks its own subset of it as its Functional Structure. The Taxonomy section of the console is where super admins maintain that shared library. Workspace roles never change it; a workspace only edits its own rows.
Where to find it
Taxonomy in the console sidebar (/admin/taxonomy), for console roles holding Taxonomy view; creating, editing, archiving and linking need Taxonomy Act (the seeded Owner, or a custom role such as a Taxonomy editor). Pick a type (sectors, sub-sectors, job families, technical competencies, general competencies, position templates), then search by name or slug and filter by status (Active, Archived, All).
What you can change
| Type | What the console can do |
|---|---|
| Sectors, sub-sectors, job families, technical and general competencies | Create; edit Arabic and English names and descriptions; archive and unarchive |
| Position templates (the global job library) | Archive and unarchive only |
| Links between them | Add only |
| Job descriptions and positions | Nothing — they belong to each workspace |
Creating a row asks for the Arabic and English names (and descriptions where the type has them):
- A new sub-sector belongs to a sector.
- A new job family must be placed under at least one sub-sector.
- A new competency must be linked to at least one job family; otherwise no workspace could ever see it.
Links you can add: sub-sector → job family, sector → job family, job family → technical or general competency, and a sector's rubric for a technical or general competency. Links are labelled "affects new adoptions only".
What a change does to workspaces
This is the part to understand before you save.
- Edits show everywhere. A new name or description appears at once in every workspace that uses the row, in pickers, Functional Structure screens and job description cards. Before saving, the edit dialog shows how many workspaces use the row.
- Archiving hides a row from new selection only. An archived row disappears from onboarding and from every picker for workspaces that have not selected it. Workspaces that already selected it keep it, see it, and can save their structure with it as before. Archiving never removes or hides anything a workspace already has. Unarchive makes it selectable again.
- Links are add-only. You cannot remove a link or move a sub-sector to another sector. A new link applies when a workspace next adopts the family; it does not rewrite structures workspaces already built.
- There is no delete. Global rows are only ever archived, because deleting them would cascade into workspaces' job descriptions and competency links.
Names and slugs
- Every row has a slug (its stable key). The console generates it from the English name when you create a row, and it is read-only afterwards — seed data relies on it.
- Job family and competency names must be unique across the whole platform, including workspaces' own custom rows. If a name is already taken, the console tells you which workspace holds it. A clashing sector or sub-sector name is a warning you can override.
Activity
Every create, edit, archive, unarchive and link is written to the console's Activity log with the row's slug, so a change can be repeated on another deployment.