Skip to main content

Bulk changes

/settings/bulk-changes

For changes that affect many employees at once — re-orgs, mass salary adjustments, bulk department moves — the bulk change tool turns a CSV into a batch of individual change requests, each routed through its normal approval chain.

The list​

Per row: status (Draft / In review / Applied / Rejected), template type, record count, submission date.

The Create button opens a wizard:

  1. Pick a template type
  2. Upload the CSV (or download the template first)
  3. Map columns to fields
  4. Save as draft

Detail page​

/settings/bulk-changes/[id] is where validation and execution happen. Sections:

  • Template info — what change type, what fields it expects
  • CSV preview — uploaded rows; Replace to upload again
  • Record count — how many rows the file contains
  • Per-row status — Valid / Error with the specific validation message

Actions:

  • Validate — re-runs validation against the latest CSV
  • Execute — only enabled when all rows are valid; creates the underlying change requests
  • Download — the template (for the empty schema) or the results (with per-row outcomes)

Why this is gated by approval​

Each individual record still flows through its normal approval chain (per approval policies). Bulk changes don't bypass approval — they just create a lot of approvals at once. Approvers usually have a "bulk approve all from this batch" action when the batch is theirs to sign off.