PSBI
Release 01HiBobHRIS integration

Start screening in HiBob. Follow it there, too.

A configured HiBob connection lets HR begin a background check from an employee record and see each screening status return to Bob.

Justin Martin, PSBI CTOJustin MartinCTO, P51 · Product release notes
A fictional HR team starts and follows a P51 background check through a configured HiBob connection.

The customer problem

Keep the workflow where your team already works.

When screening begins in one system and status lives in another, HR teams check two places, copy updates into employee records, and answer avoidable questions about where a check stands. That is busywork, and it creates room for a handoff to get lost.

What shipped

Clearer work, fewer handoffs.

The HiBob connection can treat a configured Compliance Status change as the signal to start screening. P51 reads the employee record, routes the person to the checklist mapped to their job family, and writes status updates back to Bob as the work progresses. The employee completes the secure intake in P51; the HR team can follow the outcome from the employee record.

  • A configured field transition can trigger screening from the Bob employee record.
  • Job-family mapping applies the P51 checklist that fits the employee’s work.
  • The employee receives a secure no-password onboarding link for required forms and information.
  • Bob receives status, notes, and a PreSearch link as the workflow moves from intake through completion.

Written walkthrough

What the video shows, in plain language.

The walkthrough begins in a fictional Bob employee record. HR changes the configured Compliance Status to Enrollment Initiated, which is the signal P51 has been set up to recognize. P51 reads the employee record, applies the job-family checklist, and sends the employee a secure onboarding link. As the employee completes their part and the client reviews and submits the order, Bob receives the next status. The screen ends with the employee record showing either Compliant or Results Require Review, with a link back to P51 for the detail.

  1. 1Signal the screening request

    HR changes the configured Compliance Status field to Enrollment Initiated.

  2. 2Route the right checklist

    P51 reads the employee record and applies the checklist configured for that job family.

  3. 3Complete the secure intake

    The employee receives a no-password onboarding link to complete required forms and information.

  4. 4Follow progress in Bob

    Bob reflects Pending Consumer, Pending Client Review, Processing, Compliant, or Results Require Review as the workflow advances.

Who this is for

This is for HR teams using HiBob who want screening to start from the employee record and want recruiting or HR operations to see the next status without working in a separate queue all day.

Related services

What you'll need to get started

Your team needs to choose the Bob fields P51 should read and update, map job families to P51 checklists, and authorize the connection. PSBI works through those choices and tests the workflow with you before launch.

Questions teams ask

Release FAQ

How does a HiBob screening request start?

In the field-transition setup shown here, HR changes the configured Compliance Status field to Enrollment Initiated. P51 recognizes that configured change and starts the mapped workflow.

Does P51 pull an employee’s SSN or date of birth from HiBob?

No. The employee completes the secure P51 onboarding flow for the information required by the ordered checks.

What status can Bob show?

The configured connection can write statuses including Pending Consumer, Pending Client Review, Processing, Compliant, and Results Require Review, along with notes and a link back to P51.

Is the HiBob Marketplace listing available?

This release covers the configured HiBob connection. Marketplace availability and tenant rollout should be confirmed with PSBI before making plans around a listing.

Justin Martin, PSBI CTO

A note from Justin

Why we built this.

The point of an HRIS connection is not to add another integration logo. It is to let the person doing the work start screening where they already work, then see what needs attention without chasing a status through email. That is what we built this around.

Justin Martin · CTO, P51

Product updates

Get P51 releases in your inbox.

Short product updates when we ship something your team can use.