Skip to content
On this page 7 sections

Recruitment

Recruitment connects job postings, applications, interviews and offers. The current workspace interface is still being built, so this overview explains availability and key distinctions rather than asking you to complete unavailable tasks.

Access needed

Access depends on your assigned permissions and workflow scope.

Read recruiting records when the interface is available
recruitment.read

The Recruitment plan feature is required. The current placeholder screens do not provide record browsing.

Role and permission labels

Typical responsibility: Authorized recruiting reader. Role names alone do not grant access.

  • Read recruitment records
Create or manage postings and applications when available
recruitment.manage

Reading records separately needs recruitment.read. Workflow state and plan conditions still apply; these controls are not implemented in the reviewed interface.

Role and permission labels

Typical responsibility: Authorized recruiter. Role names alone do not grant access.

  • Manage recruitment records
Use documented employee self-service when available

An authenticated employee link and eligible posting are required for internal applications/referrals. This does not grant recruiter-wide access. A working internal board is not exposed in the reviewed interface.

Role and permission labels

Typical responsibility: Employee. Role names alone do not grant access.

Demo screenshots may show broader access than your account.

Check availability in your workspace

Open Talent → Recruitment → Job Postings. If the page says This page is not yet implemented, there is no recruitment setup you can complete there. Coordinate hiring through your organization's current process and ask your administrator about feature availability.

Current Recruitment availability
The current page is a placeholder; no posting was created.

This screenshot shows the current application rather than a simulated hiring dashboard. Detailed how-to instructions and populated workflow screenshots will be added when the corresponding screens are available.

Understand the documented hiring workflow

The documented service supports the following sequence. This describes the intended workflow; these steps cannot currently be performed through the placeholder screens shown above.

  1. Prepare a job posting

    Define the role, description and intended audience. New postings start as Draft.

  2. Publish deliberately

    A posting moves from Draft to Published, then Closed. Internal and external visibility are separate choices.

  3. Collect and review applications

    Applications can be recruiter-recorded, submitted through careers, submitted internally or referred by employees. Applications belong to a posting and move through its pipeline.

  4. Interview and review offers

    Interview feedback and offer approvals have their own assignment and workflow rules. Being able to read a posting does not grant every hiring action.

  5. Verify the hire separately

    Offer acceptance and employee creation are separate stages. Check that hiring completed successfully before treating the candidate as an employee.

Keep publication and visibility separate

A closing date can stop a posting appearing on the public and internal boards without changing its status to Closed. Closing a posting does not by itself end work on applications already received. A Closed posting cannot be reopened through the documented lifecycle.

Employee applications and referrals

The documented internal job board allows linked employees to apply or refer candidates without general recruiting administration permissions. That is different from access to the recruiter-wide application list. The current interface reviewed here does not expose a working internal job-board workflow, so this guide does not direct employees to an unavailable Apply button.

Ask HR where internal opportunities and referrals should be submitted while the interface is unavailable. Do not send candidate files through unrelated document uploads merely to imitate a recruitment application.

Recruitment Onboarding and employee journeys

The Recruitment → Onboarding page is currently a placeholder. Existing employee journeys are a separate workflow for assigned onboarding and other employee tasks. Do not assume the Recruitment placeholder replaces that working employee feature.

Troubleshooting

What you seeWhat it means
Coming soon or not yet implementedThe current screen has no working recruitment workflow.
Recruitment is unavailable under the planAsk your administrator to check plan inclusion; permissions alone do not enable it.
A menu item is visible but has no formsNavigation visibility does not establish that the feature is implemented.
An employee needs to apply internallyAsk HR for the current process; the reviewed interface has no working internal board.
Recruitment Onboarding is emptyUse employee journeys only for their documented employee-task workflow.