Set up the Staffing pack
What an administrator turns on and configures before recruiters can work — enablement, stages, custom fields, and working permissions.
Staffing is a vertical pack, not a module every organization gets. Its six record types — Client, Vendor, Consultant, Requisition, Submission and Assignment — only exist once the pack is enabled for your organization.
This article is the administrator half. Recruiters should start at Staffing overview instead.
1. Enablement comes first
Until the Staffing pack is on, the Staffing section does not appear in
navigation and its pages are not reachable. That is enablement, not a
permission problem — granting someone staffing.requisitions.read on an
organization without the pack changes nothing.
Once the pack is on, each Staffing record type becomes available to the shared settings surfaces below, because the pack declares that each one supports pipelines, custom fields, workflows, saved views, tags, ownership and visibility.
2. Configure stages before anyone creates work
Staffing records move through stages you define, not a fixed lifecycle. Set them up in Pipelines — requisitions, submissions and assignments each get their own.
Do this before recruiters start. If a record type has no configured stages, creation is blocked with a link back to Settings rather than allowed into a dead end, and the pipeline has nothing to lane up.
3. Add the fields your firm actually tracks
Every Staffing record type supports custom fields. They appear across create, edit, detail, import, reporting and export together — there is no separate switch for any one of those surfaces.
Staffing entities show up in the custom-field entity picker only when the pack is enabled.
4. Understand where rates live
A Consultant carries the bill and pay rates your firm currently associates with that person, expressed in USD per hour. An Assignment carries the bill and pay rates agreed for that placement, together with its currency and rate period.
A Submission has no rates. It records that a consultant was put forward for a requirement and how that decision progressed; the placement commercials belong on the Assignment created at conversion.
There is no separate rate permission. Anyone who can read the Consultant or
Assignment can read its rates, and anyone who can manage that record can edit
them. Requisition target ranges and custom fields classified as rates remain
behind staffing.rates.view / staffing.rates.manage. Use the normal record
permissions in the next section to control operational rates.
5. Grant the working permissions
Each record type has its own read, manage and transition permissions — for
example staffing.requisitions.read, .manage and .transition. Transition
is what allows a stage move, so a user with manage but not transition can edit
a record and still be unable to advance it.
Two extras are worth calling out:
staffing.submissions.convert— turning an accepted submission into an assignment. This is the placement moment; scope it to the people accountable for it.staffing.import.manage— running imports.
Set these up in Permissions.
5a. Staffing records can now write CRM records
A recruiter editing a Client, Vendor or Consultant sees the CRM company or person fields on the same form as the staffing ones, and creating a role can create the company or person alongside it. Client and Vendor records can also create or attach contacts at their company.
Those halves are governed by the CRM permissions, not the Staffing ones:
- Company editing (
accounts.edit) — change a Client's or Vendor's company fields from the staffing record. - Contact editing (
contacts.edit) — correct a Consultant's person fields. - Contact creation (
contacts.create) — add a new person from a Client or Vendor record, or create a person while creating a Consultant.
Someone without the matching CRM permission still sees those fields, read-only, and can work the staffing half normally. Nothing is refused mid-save, and no Staffing permission grants the ability to change CRM truth on its own.
Custom fields you add to CRM accounts and contacts appear on these staffing surfaces too, because they render the same CRM field registry.
6. Optional: workflows, tags and saved views
Staffing entities are available to workflows, tags and saved views on the same terms as CRM records. Nothing here is Staffing-specific — if the pack is enabled, the entities are simply in the list.
Vocabulary note
Requisitions are labelled Requisitions in Full mode and Requirements in Simple mode. This is pack vocabulary, not two record types, and it is why help articles and screens may not use identical words.