The Platform Console sits above every workspace on a Jadiroon deployment. From it, platform super admins see the whole platform at a glance, create workspaces and their first administrators, manage users in any workspace, maintain the shared global taxonomy, and step into a workspace when they need to work inside it.
This section is for super admins. If you work inside a workspace, you will not see the console; the one part of it that concerns you is the Super admin activity tab of your workspace's Audit log.
Who can use it
Super admins are separate from workspace accounts. A super admin belongs to the deployment, not to any workspace, and holds one console role. A console role grants View or Act per console section, and optionally Enter a workspace with an entry role. Two roles come ready:
- Owner (locked) — full access: every console section, every change, and entering workspaces as their Workspace Admin.
- Viewer — read-only access to Overview and Workspaces. Built for executives who need consolidated indicators across all workspaces. A Viewer cannot change anything and cannot enter a workspace.
Owners can create more, for example a Taxonomy editor or an HQ Recruiter who enters workspaces as Talent Acquisition. See Console roles. Every limit is enforced on the server, not just hidden in the interface.
A client that holds super-admin keys always has its own dedicated deployment, so a super admin sees every workspace on that deployment. On the shared jadiroon.com, only the Jadiroon team holds super admin.
Signing in
The console has its own sign-in page at /admin/login, separate from the workspace login. Its session is separate too: you can keep the console open in one tab while you work inside a workspace in another, and a workspace session never opens the console (or the reverse).
- Your password must be at least 12 characters. You set it when you open your activation link (see Super admins and handover).
- After the password, every sign-in asks for the 6-digit code from your authenticator app. Two-factor is always on for super admins and the console never remembers a device (see Super admins and handover).
- A console session lasts 12 hours, then you sign in again.
- Sign out ends your console session in every browser, along with any workspace visit you have open. Copied or old sessions stop working too.
- Repeated failed sign-ins are rate-limited.
- The console has its own Arabic / English toggle in the sidebar.
The sections
Each section appears in the sidebar only for roles that hold its View permission; changes need Act.
| Section | Owner | Viewer | What it is for |
|---|---|---|---|
| Overview | ✔ | ✔ | Platform totals and a per-workspace indicator table |
| Workspaces | ✔ edit | ✔ read | List, create, edit, suspend, reactivate, delete, restore; enter a workspace (a separate permission) |
| Users | ✔ | — | Users and pending invitations across all workspaces |
| Taxonomy | ✔ | — | The shared global taxonomy library |
| Super admins | ✔ | — | Super admins (invite, change role, step out and back in) and the Roles tab |
| Activity | ✔ | — | The log of every console action |
| Integrations | ✔ | — | Deployment-level read integrations: keys, webhooks, delivery log (Act only). See Console integrations |
| Security | ✔ | ✔ | Your own two-factor; open to every super admin |
Overview
The Overview shows platform totals at the top: workspaces (active and suspended), users by role (staff counted by workspace role: each seeded role across all workspaces, plus custom roles together; then employees, candidates and trainers), open positions, candidates, applications, hires in the last 30 days, and employees.
Below them, a table lists every workspace with the same indicators, its status and its last activity. Two tools make it useful for a group of organisations:
- Group filter and subtotals. Each workspace can carry an optional group label (for example "Central Region" or "Health"). Filter the table by group, and the table shows a subtotal per group. A group is a reporting label only; it grants no access.
- Export CSV. Downloads the table as it is filtered, for reporting outside the platform.
Workspaces
The Workspaces list shows active and suspended workspaces, with search by name or slug and a group filter. A Deleted filter shows soft-deleted workspaces so a role with Workspaces Act can restore them.
Open a workspace to see its detail page: profile (name, slug, language, organisation size, sector, group, creation date, whether onboarding is complete), its indicators, its users (with their workspace roles), and — for roles with Workspaces Act — Edit profile and the Lifecycle actions, plus Enter workspace for roles that may enter.
Edit profile lets you change the name, language, organisation size, group, brand colour, logo URL and the "Hide the Jadiroon footer on public pages" option. The slug cannot be changed after the workspace is created.
Activity
Every console action writes an entry to the activity log: workspace created, edited, suspended, reactivated, deleted or restored; a workspace entered or exited; a user invited, re-invited, given a new role, disabled, enabled, removed or sent a password reset; a taxonomy row created, edited, archived or linked; a super admin invited, changed, stepped out or back in; a console role created, edited or deleted; and server-side bootstrap runs. Filter by super admin, workspace and action. An action taken by a deployment-level integration belongs to no workspace, so it shows here, unfiltered, with the actor Deployment-level integration · <name> (its keys are read-only today, so none appear yet).
Filtered to one workspace, the log also shows that workspace's own audit trail: its users' changes, sign-ins and exports. A change made through the workspace's public API shows its actor as Integration · <integration name>. Actions that touched a workspace also appear, read-only, in that workspace's Audit log under Super admin activity. Super-admin activity is never hidden from the workspace it concerns.