Workspaces are created only from the Platform Console, by a super admin whose console role holds Workspaces Act. There is no public sign-up. Each new workspace starts with a single role, the locked Workspace Admin, and gets its first Workspace Admin by invitation: that person receives an activation link, sets a password and starts working.
Where to find it
Workspaces → New workspace in the console (/admin/workspaces/new). Needs Workspaces Act.
The form
Workspace
- Name — the organisation's name, shown across the workspace and on its public pages.
- Slug — the URL prefix (
/{slug}/...). Suggested from the name and checked for availability. It cannot be changed after the workspace is created. - Language — Arabic or English. Used for the workspace's default language and for the activation email.
- Organization size — optional.
- Group — optional reporting label (for example "Central Region"). Existing groups are suggested. It groups workspaces on the Overview and grants no access.
- Sector — optional. Only global, non-archived sectors are listed. Leave it as "Chosen during onboarding" to let the first admin pick it.
Copy configuration from
- Nothing — start empty creates a standard empty workspace.
- Or pick an existing workspace to copy its configuration once (see below).
First admin
- Full name and Email of the person who will be the workspace's first Workspace Admin.
Click Create workspace. When it succeeds, the console shows Workspace created with a link to open it.
Starting empty
An empty workspace gets the defaults every workspace starts with: candidate and trainer email templates, offer templates, the locked Workspace Admin role (its only role) and starter work-time profiles. Its first admin builds every other role under Settings → Users & roles → Roles, ideally before inviting the team, and goes through the normal four-step onboarding (sector, sub-sectors, job families, job descriptions) on first sign-in, which builds the workspace's Functional Structure. If you chose a sector on the form, it is already set when onboarding starts.
Copying from an existing workspace
Use this when a new organisation should start from the setup of one you already have — for example, a new cluster that should match its headquarters. The copy happens once, at creation; there is no sync afterwards.
What is copied:
- Settings — workspace settings and thresholds, scoring configuration, report style, brand colour and footer (not the name and not the logo).
- Templates — candidate and trainer email templates and offer templates.
- Roles (every role of the source, with its permissions and data scope) and work-time profiles. The new workspace starts with the source's roles instead of Workspace Admin alone.
- Pay scales, with their grades and steps.
- The Functional Structure — the operating sector, the selected sub-sectors and job families (with their competencies and mandates), and the source's job descriptions with their competencies, responsibilities, KPIs, contacts and evaluation.
How custom rows are handled:
- Global taxonomy rows are reused as they are.
- Job families and competencies the source workspace created itself are cloned as new rows owned by the new workspace and named
<name> (<new workspace name>), so names stay unique. A custom sector or sub-sector of the source's own sector is cloned too. - References to another workspace's custom rows are dropped.
Because the Functional Structure arrives ready, the new workspace skips onboarding. Its first admin lands straight in the app.
If the source workspace has no sector yet, only the settings, templates, roles, work-time profiles and pay scales are copied. No structure is copied, and the first admin goes through onboarding as usual.
What is never copied: people, users, invitations, candidates, applications, positions, assessments, the Organizational Structure (org units), or any other record. A copy carries configuration, not data.
You cannot copy from a deleted workspace; it is not offered in the list.
The first admin's activation
The first admin receives an invitation email in the workspace's language with an activation link, valid for 7 days. Opening it, they set a password (at least 8 characters) and then sign in. Their email counts as verified, so no separate verification email is sent.
- An empty workspace sends them through onboarding on first sign-in.
- A workspace copied from another one opens directly on its home page.
If the link expires or gets lost, resend it from Users (filter by the workspace, find the pending invitation, Resend). Resending issues a new link and the old one stops working. See Managing users across workspaces.
From then on, the workspace's own administrators build their roles, invite the rest of their team and bulk-load their employees with the in-app tools.
Next
- Managing users across workspaces
- Creating your workspace — the same process from the first admin's side