On this page0
Unfamiliar word? See Glossary: words used in these docs. Looking for the tasks in order? Begin at Start Here.
Reference
Included in: Team and Advanced. Which Plan Includes What
Requisitions & Careers Page
This page describes requisitions and the budget approval, who owns a requisition or a candidate, the careers page, job alerts and job-board feeds. Recruitment is included from the Team plan. This page is part of the reference Recruitment & Hiring.
What It Does
- The budget approval. A new requisition waits on finance. A person who manages finance, and who did not create it, approves or refuses the budget. Refusing needs a reason, which the requester sees on the requisition and by email. After a refusal the terms can be edited and the requisition resubmitted.
- Open internally or publish. With the budget approved, a role can be opened internally, with no public listing, or published on the careers page and in the job-board feeds. A published role can be unpublished and keeps hiring internally. A role on hold takes no new applicants until hiring is resumed.
- A dated record. Each requisition keeps a record of who requested, approved, refused and resubmitted it.
- Owners. Each requisition and each candidate has an HR owner. The owner is one of the things that decides who can see a candidate. Each reassignment is written to the audit log.
- The careers page. Only published roles appear. You set the company introduction and a few short facts, and two switches turn on job alerts and general applications. A visitor who asks for job alerts is sent nothing until they confirm their email address.
- Applications. An application from the careers page carries one résumé file of up to 5 MB.
- Job-board feeds. Three public addresses list your published roles for job boards and search engines. They need no login and change by themselves as you publish or close roles.
Requisitions And The Budget Gate
A requisition is a request to hire for one role. It is created on HR & TalentJob Postings by a person who manages recruitment and cannot be opened or published until its budget is approved. The page sorts requisitions into “Ready to publish”, “Awaiting budget”, “Budget refused”, “Live” and “Filled / closed”, and each one shows its own progress: Drafted, Budget approval, Publish, Hiring, Filled.
Finance Decides The Budget
After A Refusal
Open Internally Or Publish
The Requisition Page
Who Owns A Requisition Or A Candidate
Each requisition and each candidate has an HR owner, shown as “HR Owner”. A person who manages recruitment clicks the reassign button beside it, picks a person under “HR owner” (or “Unassigned”) and clicks “Reassign”. The owner matters because it is one of the things that decides who can see a candidate. On a requisition, ticking “Also move existing candidates in this pipeline” moves the candidates that belonged to the previous owner or to nobody; candidates individually reassigned to someone else are left as they are. Each reassignment is written to the audit log.
Careers Page, Job Alerts And Job-Board Feeds
Your instance serves a public careers page, with one page per role. Only roles with the status Published appear. The “Careers page & job-board feeds” card at the top of HR & TalentJob Postings has “Preview careers page”, “Edit careers page” and an arrow that shows the feed addresses.
Edit Careers Page
Job Alerts
General Applications
Applications
Job-Board Feeds
Three public addresses list your published roles for job boards and search engines. They need no login, are rate-limited, and change by themselves as you publish or close roles. Copy each full address from the card and give it to the job board. The paths behind the three addresses are listed under Technical detail below.
| Label On The Card | Use |
|---|---|
| Indeed feed (XML) | Submit this address in your Indeed employer account as an XML feed. |
| LinkedIn feed (XML) | Give this address to LinkedIn as your jobs XML source. |
| Google Jobs (JSON-LD) | Structured data for search engines. |
If something here is not working as you expect, start with When something goes wrong.
The plain explanation is above. This part is for IT and developers: the exact settings, permission names, API addresses and data fields behind it. Closed: select the heading above to open it. While it is closed, your browser’s find-on-page (Ctrl+F or Cmd+F) does not search this part.
Routes, Permission Checks And Refusal Codes
Where the sections above say “a person who manages recruitment” or “is refused”, this is the permission that is checked and the answer the API gives. Paths are written as in the API reference.
Requisitions And The Careers Page
Creating a requisition, editing and resubmitting its terms, the Posting & feeds tab, reassigning an owner and editing the careers page all need manage_recruitment. Budget routes: POST /recruitment/job-postings/:id/approve-finance and /reject-finance need manage_finance; approving your own requisition answers 403 with the code FINANCE_SELF_APPROVAL unless you are an administrator. POST /job-postings/:id/resubmit-budget and PUT /job-postings/:id/owner (body { ownerId, cascade? }) need manage_recruitment. GET /job-postings/:id/activity is open to manage_recruitment, view_recruitment and manage_finance. Careers settings are GET and PUT /recruitment/careers-settings. The public job page route accepts numeric ids only.
Job-Board Feed Addresses
The three feeds described under Job-Board Feeds above, with the paths as they are written in the API reference.
| Label On The Card | Address |
|---|---|
| Indeed feed (XML) | GET /recruitment/public/jobs/indeed.xml |
| LinkedIn feed (XML) | GET /recruitment/public/jobs/linkedin.xml |
| Google Jobs (JSON-LD) | GET /recruitment/public/jobs/jsonld. One role is at /public/jobs/:id/jsonld. |