> ## Documentation Index
> Fetch the complete documentation index at: https://docs.integratewise.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# HR User Flow: Practitioner Path Through the Workbench

> Follow the Human Resources practitioner journey from entry to continuation across the Spine Workbench, adapted for recruiters and HRBPs.

The HR user flow maps how practitioners move through the Spine Workbench to complete people tasks. It preserves continuity across sessions, so a recruiter who steps away from an offer draft returns to the exact same context.

<Steps>
  <Step title="Enter">
    Log in to SpineWorkspace and land on the HR domain home. Your role determines the default tab: Pipeline Board for recruiters, People Queue for HRBPs, or Onboarding Queue for People Ops.
  </Step>

  <Step title="Discover">
    Twin surfaces what needs attention: candidates stuck in stage, reviews approaching deadline, or pending offer approvals. You do not need to query each system.
  </Step>

  <Step title="Understand">
    Drill into a candidate, employee, or task. Spine assembles context from Workday, Greenhouse, and other sources so you see history, relationships, and open items in one place.
  </Step>

  <Step title="Contextualize">
    Add notes, attach documents, or tag stakeholders. Twin records your intent and links it to the relevant entity for future sessions.
  </Step>

  <Step title="Decide">
    Choose the next action: move a candidate, launch a review, or approve an offer. Twin may suggest options based on policy and past behavior.
  </Step>

  <Step title="Act">
    Execute the action through a governed capability. The system checks authorization, scope, and policy before writing back to the source system.
  </Step>

  <Step title="Review">
    Confirm the outcome: candidate stage updated, review launched, offer approved. Receipts are stored for audit.
  </Step>

  <Step title="Continue">
    Hand off to a colleague or resume later. Context, memory, and notes persist across people, sessions, and agents.
  </Step>
</Steps>

<Warning>
  Actions that write to source systems may require human approval depending on the capability scope.
</Warning>

## Related

* [Human Workbench](/internal-docs/domains/human-resources/human-workbench)
* [AI Flow](/internal-docs/domains/human-resources/ai-flow)
* [Execution Flow](/internal-docs/domains/human-resources/execution-flow)
* [How It Works: Continuity](/how-it-works/continuity)