Workspace settings

For HR administrators

Workspace settings collects the per-workspace configuration that does not belong on a more specific page — the workspace's display name, default locale, branding, and a few operational toggles.

Where to find it

/{slug}/app/settings. The settings index shows only the cards your role can open: Workspace, Users & roles, Work time, Hire settings, Integrations, Courses & programs, Develop settings, AI Prompts and Audit log. This page covers the first. (Your sector and competency taxonomy are managed from their own sidebar sections — see Competency taxonomy.)

What is on the Workspace card

/{slug}/app/settings/workspace — editable for roles holding Settings & integrations Act (the Workspace Admin by default), read-only for everyone else who can open it. The card surfaces four core settings:

  • Workspace name — editable text input (1-80 chars). Appears in the top bar, on public job pages, and in candidate emails.
  • Default locale — AR / EN toggle. Used for new invitations that do not specify a locale, and for stage emails when no user-level preference exists.
  • Workspace logo — upload PNG / SVG / JPG / WebP up to 2MB. Stored on managed cloud storage; the URL is persisted to Workspace.brandingLogo immediately. Appears in the top bar and on public job pages.
  • Hide “Powered by Jadiroon” on public pages — checkbox. When enabled, the small attribution in the footer of the public jobs and apply pages is suppressed. Aimed at enterprise clients (Aramco, STC, SAMA, sovereign ministries) who require a fully white-labelled candidate experience. Persists to Workspace.brandingHidesFooter.
  • Default calendar — Hijri / Gregorian / Both. Stored on the device in a jadiroon_calendar cookie (mirrored to localStorage). The cookie lets server-rendered pages honor the choice too, so the calendar applies across the whole admin dashboard. A workspace-scoped field is on the v1.x list once schema work catches up.

Workspace identity

  • Display name — what appears in the top bar wordmark, on candidate emails, and in the public job page header. Editable.
  • Slug — the URL prefix (/{slug}/). Set when the workspace is created; not editable in v0.5. Slug changes break in-flight links and are deferred to v0.6 with a redirect-management UI.

Locale defaults

  • Default workspace locale — used for new invitations whose locale was not specified, and for stage emails to candidates who did not specify a locale on application.
  • Currency for cost displays — Saudi Riyals (SAR) by default. Used in the learning catalogue cost bands and any other currency-bearing surface.

Per-user locale (each individual's interface language) is set on each user's profile, not here.

Branding

  • Workspace logo — uploaded as an image (PNG with transparent background recommended, up to 1MB). Appears on the public job page, on the welcome email to new hires, and in the workspace's top bar (next to the wordmark, not replacing it).
  • Accent colour — hex value used on the public job page's primary action button. The administrative workspace and employee portal use the platform's standard editorial palette regardless.

If you do not upload a logo, the public job page uses the workspace name in display type — a respectable fallback that requires no asset.

Saudization settings

The Nitaqat activity set is no longer managed here — a workspace now declares as many Nitaqat economic activities as it operates, and tags employee seats to them, on the People → Saudization page (/{slug}/app/people/saudization). See Saudization.

This card keeps one related field:

  • Sector — the SSF competencies sector your workspace operates in (e.g., Health, Digital, Manufacturing). This drives the competencies taxonomy (subsectors, job families, competency catalogues); it is distinct from the Nitaqat activities declared on the Saudization page and does not affect your Nitaqat band.

Your size band for Nitaqat is not set anywhere manually — each declared activity's headcount is detected automatically from its live tagged seats, so its thresholds always track its real headcount. (The organization size you choose during onboarding — Small / Medium to small / Large / Huge — is a separate descriptor; see the Organization size section below.)

Organization size (onboarding)

Your organization size (حجم المنشأة) is set when your workspace is created, and you can confirm or change it during onboarding:

SizeIndicative headcount
Small (متناهية الصغر)1–9
Medium to small (متوسطة إلى صغيرة)10–99
Large (كبيرة)100–500
Huge (عملاقة)501+

The size is a lightweight descriptor. It is independent of the Nitaqat size band above.

Calendar preference

/{slug}/app/settings/workspace → Default calendar. Three options:

  • Gregorian only — dates across the admin dashboard show Gregorian dates.
  • Hijri only — dates show Hijri dates.
  • Both — dates show both, Hijri first. This is the recommended setting for Saudi-market workspaces.

The preference is stored per-device (cookie + localStorage) and applied across the admin dashboard — both client components (via DateLabel) and server-rendered pages (via the cookie). When no choice has been made, dates follow the UI language: Arabic defaults to Hijri, English to Gregorian. Public, candidate-facing pages follow the viewer's own locale rather than the workspace preference.

Two-factor requirement

Workspace Admins also see Require two-factor authentication for all staff on this card; only they can change it. It is on by default, and Workspace Admins always sign in with two-factor regardless. Details: Requiring two-factor for your workspace.

Users, roles and the audit log

Two other settings cards govern access and accountability:

  • Users & roles: members, invitations and the workspace's roles. See Team management and Roles and permissions.
  • Audit log: who did what, to which record and when, including super-admin visits, with filters and CSV export. See Audit log. Every change on this Workspace card is recorded there with its before and after values.

Operational toggles

A small set of binary settings:

  • Allow employees to set their own target role. Default on. Off means the target role can only be set by HR or a line manager.

What is not in v0.5

  • Custom domains for the public job page. The page is at {slug}.jadiroon.{tld}/jobs in v0.5. Custom domains (careers.yourcompany.sa) are on the v0.6 watch list.
  • SAML/OIDC SSO configuration. No SSO yet.
  • Organisation-level grouping (multiple workspaces under one parent). Each workspace is independent in v0.5; multi-workspace governance is a v0.6+ topic.

Next

Section VIII — Concepts and vocabulary opens the reference part of the manual, defining every load-bearing term you will encounter elsewhere.