How-to · HR-driven lifecycle

HR hires. HR moves. HR ends.
Access follows, automatically.

When HR is the source of identity, onboarding is a sync instead of a ticket queue. Monosign reads employees and org units straight from your HR system’s API, assigns access by department, provisions it into downstream apps over SCIM, and takes it back the same way when someone changes teams or leaves.

  • HR API as a user source
  • Department-to-access triggers
  • SCIM provisioning
Walkthrough

From an HR record to working access.

Five steps, verified end to end: hire, transfer, and termination all flow through without a ticket.

  1. 01

    Connect the HR system as a user source

    Point Monosign’s web API user provider at your HR system’s employee endpoint: map identity, user name, and email columns, add the auth headers, and set the paging fields. Full and incremental syncs run on their own schedule, with an incremental filter keyed to the HR system’s change timestamps.

    Tip — The walkthrough behind this guide was verified end to end against the UKG Pro Personnel API shape; for your tenant only the base URL and credentials change. HR users sync with login disabled: HR is a source of identity, not a sign-in path.
  2. 02

    Map the profile and the org tree

    Map HR fields to the Monosign profile: name, job title, department, employee id, manager, and start date. Sync org levels as groups, so department membership in HR becomes group membership in Monosign.

  3. 03

    Connect downstream apps over SCIM

    Add each application as a SCIM entitlement source. After the first sync, the app’s own groups appear in Monosign as entitlements you can assign, and provisioning flows through standard SCIM calls.

  4. 04

    Turn departments into access with triggers

    Create a trigger per rule: membership in the HR group for Engineering assigns the SCIM app’s Engineering group; Sales maps the same way. Triggers react to both directions, and the deprovision policy takes access back when the membership goes away.

    Tip — Because the trigger watches membership change events in both directions, a department transfer is just one revoke and one assign: no separate mover workflow to build.
  5. 05

    Run the three scenarios

    Hire someone in HR and watch the user, group, and application access appear. Transfer them and watch access move. Terminate them and watch the sync remove the user and the trigger take back everything the source owned. A rehire with the same employee number reactivates the same identity.

Ready for the full picture?

The complete walkthrough — with every screenshot, every flag, and version-specific notes — lives in our help center.

Continue in the full docs

Ready to start managing
identities the right way?

Spin up a fully-loaded trial tenant in under five minutes. No credit card. No sales gate.