Skip to main content

HR Source Precedence

When identity data arrives from more than one authoritative source (an HR system, a directory, a SCIM feed), precedence rules decide which source wins for each attribute — so conflicting updates resolve deterministically instead of last-write-wins chaos.

Admin console: /admin/hr-source-precedence

Concepts​

  • Source — an authoritative system feeding identity attributes (e.g. HR, Entra, a SCIM client).
  • Precedence order — the ranked list of sources. Higher-precedence sources override lower ones for a given attribute.
  • Per-attribute resolution — precedence can differ by attribute (HR may own title, the directory may own email).

Admin-configured, not seeded​

Precedence is created by an admin — there is no default order. Most companies run a single HRIS and need no precedence at all: with no order configured, every source ranks equal and the merge simply resolves latest-wins. Configure an order only when you genuinely run more than one authoritative source.

How it works​

As updates arrive (HR sync, SCIM, directory integration), the precedence engine resolves the final value for each attribute by consulting the ranked sources — a higher-precedence source's value is not overwritten by a lower one. Sources not in the list (or when no list exists) are lowest precedence and only fill empty fields; equal precedence resolves latest-wins.

Typical setup​

  1. /admin/hr-source-precedence → Add source for each HRIS you run, ordered highest-first.
  2. Save Precedence (this creates the order row on first save).
  3. Inbound updates now resolve against these rules. Single-HRIS deployments can skip this entirely.
  • Reconciliation — verify downstream systems match the resolved record.