HRIS with YeshID

Last updated: June 23, 2026

Connect your HRIS (Human Resources Information System) to YeshID so that your HR system becomes a source of truth for who works at your company. Once connected, YeshID imports your employees, keeps their records in sync, and can automatically kick off onboarding and offboarding the moment someone is hired or leaves.

An HRIS connection is a good fit when HR already owns the canonical record of each employee (their start date, end date, manager, department, title) and you want that record to drive access in YeshID instead of maintaining a second list by hand.

Plan note: HRIS management is available on Business plans and above. If you don't see the options described here, your organization may need to upgrade.

What HRIS Provides

  • One source of truth for people. Employees come from your HRIS, so the people in YeshID match the people in HR — automatically.

  • Hands-off onboarding. A new hire in your HRIS can trigger an onboarding workflow in YeshID, scheduled to run on (or before) their start date.

  • Hands-off offboarding. When someone is given a termination/end date in your HRIS, YeshID can stage or run their offboarding workflow so access is cleaned up on time.

  • Always-current records. Each sync updates names, titles, departments, managers, and dates, so your people data doesn't drift.

  • You stay in control. You decide which employees become YeshID people, whether they start active or staged, and exactly how HRIS fields map onto your YeshID person records.

Key terms

Term

What it means

People source

The setting that tells YeshID where your people records come from. A people source is either a directory (e.g. your identity provider) or an HRIS. You can have more than one.

HRIS people source

A people source backed by a connected HRIS application. It imports employee records and can drive lifecycle workflows.

Employee

A record imported from your HRIS. Employees appear in the Employees tab of the connected app and may or may not be linked to a YeshID person.

Import Employees

The action on an HRIS-capable application that pulls employee records into YeshID. This is what a sync runs.

Mapping

The rules that connect a field in your HRIS (e.g. "hire date") to a field on a YeshID person (e.g. start date).

Create rule

A filter that decides which imported employees become YeshID people. Employees that don't match are imported but not turned into people.

Person state

Whether newly created people start as Active or Staged. Staged people exist in YeshID but aren't fully activated until onboarding runs.

Trigger

A condition (for example, "start date is set") that fires an onboarding or offboarding workflow.

Supported HRIS providers

YeshID offers built-in (catalog) connectors for:

Provider

How you authenticate

BambooHR

Company domain + API key

Paylocity

Company ID(s) + credentials

Factorial

OAuth (sign-in consent)

UKG Pro

Service credentials + a configured report

Don't see your provider? You can also connect an HRIS through a custom API integration by pointing YeshID at your system's endpoints and describing how to read the fields. Reach out if you'd like help setting one up.

How syncing works

When a sync runs, YeshID:

  1. Pulls employee records from your HRIS via the Import Employees action.

  2. Maps each external field onto the matching YeshID person field, using the mapping you configured.

  3. Applies your create rule to decide which employees become (or update) YeshID people.

  4. Updates linked people with the latest values — name, title, department, manager, start date, and end date.

Sync is polling-based, not instant: YeshID checks your HRIS on a schedule (or whenever you run a sync manually from the Employees tab), rather than reacting to a live webhook. Every employee needs an external ID (a stable identifier from your HRIS) — records without one are skipped.

Commonly synced fields include first name, last name, preferred name, email, job title, department, location, manager, start date, and end date. You can also map HRIS fields to your own custom person fields.

Onboarding driven by HRIS

When the sync imports a new employee who matches your create rule, YeshID creates a person for them (Active or Staged, per your default). If you've connected an onboarding workflow trigger to the people source, that workflow fires when its condition becomes true — typically based on the employee's start date.

Because YeshID knows the start date, the onboarding workflow can be scheduled to run on that date (or at a set time that day) rather than the moment the record is imported, so accounts and access are ready right when the new hire needs them.

Offboarding driven by HRIS

When an employee is given a termination/end date in your HRIS — or marked inactive — the next sync writes that change onto the linked YeshID person. If you've connected an offboarding workflow trigger, the end date can stage or run the offboarding workflow so access is removed on schedule.

If a date changes in your HRIS after a workflow is already staged (for example, a last day moves up), YeshID keeps the staged offboarding in step with the new date and notifies the admin, so timing stays accurate.

Getting started

Setting up an HRIS connection takes about 10–15 minutes. You configure everything inside the connected application's Import Employees action — a short, three-step wizard (Map fields → Who to create → Review) — then activate it. The application's Employees tab then becomes your ongoing monitor for the import.

The exact wording of some buttons and tabs may shift as the product evolves — follow the flow rather than the precise label.

Before you begin

  • Make sure you're on a Business plan (or higher) and signed in as an admin.

  • Have your HRIS credentials ready — an API key, company domain/ID, or the ability to complete an OAuth sign-in, depending on your provider (see the table above).

Step 1: Connect your HRIS application

  1. Add the application for your HRIS (for example, BambooHR or Gusto) from the application catalog.

  2. Open the application's integration panel and complete the Authentication section using the method your provider requires. Authentication has to be in place first — until it is, the import wizard will show "Authenticate first" and won't be able to pull records.

Step 2: Open the Import Employees action

  1. Go to the application's Employees tab. If no import is set up yet, you'll see Set up employee import with a Configure import → button.

  2. Click it to open the Import Employees action and its setup wizard. (Once an import is live, the same place is reachable via the ⚙ Configure import button on the Employees tab.)

Step 3: Map fields

This is the first wizard step. YeshID lists every field your HRIS provides, with a sample value, and lets you decide where each one lands on a YeshID person.

  • Standard fields map automatically. External ID, first/last name, work email, start date, end date, and manager are recognized and mapped to the matching YeshID person fields for you.

  • External ID, first name, and last name are required and can't be removed — they're how YeshID identifies each person and matches them across syncs. (Email matters too; if a record has none, you'll handle that in the next step.)

  • Map extra fields to title, recovery email, address, timezone, or a custom field. Pick a target from the dropdown next to any field, or choose ＋ Create new custom field… to add one on the spot.

  • Unmapped fields are still imported onto the employee record — they just aren't written to the person. Removed fields aren't imported at all.

  • Need a field your HRIS returns but isn't listed? Use ＋ Add a field from [your HRIS]… to bring in any raw column.

Click Continue when your mapping looks right.

Step 4: Who to create

Here you decide which imported employees become YeshID people, and how.

  1. Set your create rule under Create a YeshID person when…. Add at least one condition (for example, employee status equals Active). A rule is required — with no rule, the import creates nobody and every record stays "Filtered out."

  2. Choose the starting state under New people start as: Staged (they exist in YeshID but can't log in until activated — good for reviewing before granting access) or Active (they can log in right away).

  3. Decide how to handle missing emails. Turn on Generate an email when a record has none and set a format (e.g. {{.firstName}}.{{.lastName}}@yourcompany.com), or leave it off to skip records without an email.

  4. Read the live preview. A table below the rule updates as you edit, with filter chips showing how many records will create, update, be filtered out (didn't match your rule), or be skipped (a problem like no email or a duplicate). Click any chip to see just those records.

Click Continue when the counts look correct.

Step 5: Review and activate

The final step summarizes your setup — fields mapped, your create rule, the starting state, and email handling — alongside counts of who will be created, updated, filtered out, and skipped. It also lists any onboarding/offboarding workflows this first sync would start.

  • On first setup, the commit button reads Activate import. (If you're editing a live import, it reads Apply changes.)

  • Activating runs the first sync immediately and then keeps the import syncing automatically on a schedule. YeshID drops you on the Employees tab to watch it.

Step 6: Watch the first sync and confirm results

On the Employees tab you'll see the sync status and the imported roster. Confirm the right people were created (and check the account owner column to see which YeshID person each employee is linked to). You can re-run a sync manually from here at any time with ⚙ Configure import or the sync control.

Step 7: Connect lifecycle workflows (recommended)

To make onboarding and offboarding run automatically, link your workflow templates to the people source via triggers:

  • An onboarding trigger fires for new people based on their start date, and can be scheduled to run on that date.

  • An offboarding trigger fires when an end date is set, staging or running the offboarding workflow on schedule.

Without these triggers, HRIS will still keep your people records in sync — it just won't automatically run onboarding or offboarding.

Tips and good habits

  • Start with Staged people if you want to review imports before access is granted, then switch to Active once you trust the mapping.

  • Map the manager field. Manager relationships power approvals and reporting-based access, so map it if your HRIS has it.

  • Map start and end dates — they're what let onboarding and offboarding run on time. Without them, lifecycle triggers can't schedule around the right day.

  • Tighten your create rule so contractors, test records, or not-yet-started hires don't become people before you want them to.

  • Review the preview before activating. The wizard shows exactly who will be created, updated, or skipped.

Related

  • HRIS is one of two kinds of people source; the other is a connected directory (your identity provider). You can run both, and YeshID treats each employee's source of truth accordingly.

  • Onboarding and offboarding workflows are what HRIS triggers run — see your workflow templates to control the actual tasks performed.