A Position can be born open — or saved as a placeholder. When you complete the create-a-position form with a real Job Description and an org placement, you can Open now: hiring is Open, the pipeline exists, and how visible the posting is depends entirely on the hiring pathway you chose. When the seat is still missing a Job Description and/or an org placement, you instead Save as placeholder: it is created Closed with no pipeline, flagged Placeholder, and cannot be opened for hiring until both pieces are filled in. Everything else on this page is about what happens once a Position is open — publishing, closing, reopening, and archiving.
Where the actions live
The Position detail page, /{slug}/app/positions/{positionId}. Reach it from the Positions list, or from the Positions panel on the parent Job Description.
The lifecycle buttons require the hiring permission — Talent Acquisition and HR Administrator. Everyone else with access sees the Position read-only. Every action asks for confirmation first.
Pathways decide who can see it
| Pathway | Public page | Notes |
|---|---|---|
| Internal only | Never published | The Public posting card explains this instead of showing a link, and the public URL returns not-found. Employees find the role through internal mobility. |
| Internal first | Created automatically when the window elapses | Until then the card reads Internal-only until , with a Make public now button to publish early. The window is 14 days unless you changed it in hiring configuration. |
| External | Live immediately | The card shows the URL, share text and share buttons. |
Make external on an open Position switches any pathway to External and publishes the page there and then. It is one-way — to pull a posting back, close the Position.
The Public posting card
On an open, non-archived, externally visible Position:
- The public URL —
/{slug}/jobs/p/{positionId}— with Open (preview it as a candidate would) and Copy. - AI-drafted post text — a share post in Arabic and English written from the job title and description, editable before you send it.
- Copy text, Share on WhatsApp, Share on LinkedIn.
You can also paste the URL on your careers site, hand it to a recruiter, or put it in an email. Every application through it lands in this Position's pipeline at the first stage.
What a candidate sees
The public page shows the job title, the description in the viewer's own language (falling back to the other language when you only wrote one), and a Saudi nationals only or Saudi nationals preferred chip when the parent Job Description's Saudization policy calls for it. The workspace's own brand colour and logo carry through.
The list page at /{slug}/jobs shows every externally visible Position, with the same Saudization chips and a filter to show only those roles when at least one is set.
Applying is done through the candidate portal — candidates create a free account (or log in) so they can track their application afterwards. Internal applicants are directed to apply from inside the workspace instead. See The candidate's application.
Placeholders can't be hired into
A placeholder Job Description is one not yet linked to both a sub-sector and a job family. Placeholders are excluded from the Job Description picker on the create-a-position form, and the server rejects the attempt outright — so there is no way to end up hiring into an undefined job.
Complete the Job Description (link a sub-sector and a job family; it inherits that family's competency set at the same moment) and it becomes available immediately. Its detail page offers a Complete this job description shortcut. See Placeholders.
Closing a Position
Close position on an open Position:
- hides the public posting — the URL stops accepting applications;
- closes the hiring pipeline;
- drops the Position off the Hire dashboard's active work.
Nothing is destroyed. The job description, the linked Roles, the org unit and the candidates all stay.
Reopening
Reopen on a closed Position restores hiring and recreates the pipeline if it went away. Two things will refuse it:
- No job description. Write one first — a public posting with no description is not something the platform will publish for you.
- The Position is archived. Restore it first.
Archiving and restoring
Archive files a Position away — for a duplicate, a cancelled requisition, or an org change. It works whether the Position is open or closed, and if it is open it closes hiring first, in the same step. A confirmation dialog always appears.
Archived Positions disappear from the active list, the Hire dashboard, and the candidate and employee job boards, and they become read-only (the Edit button is hidden).
They are not deleted. Archived in the Positions list header opens them with a count badge, and Restore brings one back — with hiring closed, so you reopen it deliberately when you're ready.
Archiving the parent Job Description cascades: every open Position under it is closed and their pipelines closed with it. See Archiving and restoring.
What never happens automatically
- No emails. Opening, closing and archiving are all workspace-internal. The first email waits for a candidate to act.
- No notifications. Nothing is pushed to anyone until the first application arrives.
One thing to know if you have already shared a public URL: the public page only exists while the Position is open, not archived, its Job Description not archived, and its pathway externally visible. The moment any of those stops being true — you close it, you archive it, you archive the parent Job Description — the URL stops resolving and returns a not-found page. Reopening the Position brings the same URL back.
Next
What the candidate sees when they reach the application page — useful for sense-checking the URL before you share it.