Reference · built on requestOperator by FibricWorkforce & scheduling

Onboarding Checklist

Builds the start-date checklist from the hire record and proposes account, badge, training, and paperwork tasks with owners and due dates.

Request accessPricing ↗

About

Onboarding Checklist is an operator job that starts when a hire lands in your HRIS. It reads the hire record: start date, job, location, manager, employment type. It then checks what already exists for that person in your identity provider, device management, access control, and training records, and builds the list of what does not: the account, the group memberships, the device, the badge, the courses due before day one, the paperwork the HRIS still shows open.

Each item becomes a task with an owner and a due date counted back from the start date, carried as a ticket in your work system. Account and credential steps are drafted for IT and facilities to approve; nothing is created until they do. Open items get a reminder before the start, and the record shows who did what and when.

This is a reference listing. It documents what Fibric would read from Onboarding Checklist and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Hire events from the HRIS: UKG Pro Person Hired webhook, ADP worker.hire events, Paylocity New Hire webhook, BambooHR employees/changed marked Inserted, Rippling worker-changes, Gusto employee.created
  • The hire record: start date, job, location, manager, and employment type from UKG Pro employment-details, ADP /hr/v2/workers, Workday staffing, HiBob work and employment tables
  • Identity state for the person: an Okta user and its lifecycle status, a Microsoft Entra ID user, a Google Workspace user with orgUnitPath and groups
  • Devices and badges already issued: Jamf Pro device inventory, Brivo users and credentials, Kisi card assignments, Verkada access users with start and end dates
  • Training due before day one: Deputy TrainingRecord against TrainingModule, HiBob Training table entries, or the per-role list you keep
  • Task state: Jira Service Management request status and approvals, ServiceNow request records, Freshservice tickets, Asana task completion and stories

Proposed actions

  • Target capability: propose the checklist for one hire: each task, its owner, its due date counted from the start date, and its source record
  • Target capability: propose the tickets that carry it: a Jira Service Management request, a ServiceNow record, a Freshservice ticket, or an Asana task per item
  • Target capability: propose identity steps for IT to approve: an Okta, Microsoft Entra ID, or Google Workspace user in the right org unit and groups
  • Target capability: propose access and equipment steps as tasks for their owners: a Brivo or Kisi credential, a Verkada access user, a Jamf Pro device
  • Target capability: propose a reminder in Slack or Microsoft Teams to an owner whose task is still open at your lead time before the start

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Open Jira tickets from a UKG Pro hire

    The Person Hired webhook starts the checklist. Each item becomes a proposed Jira Service Management request with its owner and due date, and the hiring manager approves the set in Slack.

    With UKG Pro, Jira Service Management, Slack

  • Stage the Okta account from an ADP hire

    worker.hire triggers a read of /hr/v2/workers. The operator proposes an Okta user matching the job and location for IT to approve, and a Jamf Pro device task for the same owner.

    With ADP Workforce Now, Okta, Jamf Pro

  • Issue a Kisi card for a BambooHR start

    employees/changed marked Inserted gives the start date. A card assignment task is proposed for the office manager, with a Verkada access user where that site uses it, and a ServiceNow record tracks both.

    With BambooHR, Kisi, ServiceNow

  • Chase open Asana tasks before day one

    Tasks created for the hire are watched through Asana webhooks. Any still incomplete at your reminder point get a proposed Microsoft Teams nudge to the assignee.

    With Asana, Microsoft Teams

Requirements

  • An HRIS connector with a hire event or change feed: UKG Pro, ADP Workforce Now, Paylocity, BambooHR, Rippling, or Gusto
  • An identity connector where accounts are proposed: Okta, Microsoft Entra ID, or Google Workspace
  • A work or ticket connector to carry the tasks: Jira Service Management, ServiceNow, Freshservice, or Asana
  • Optional: Jamf Pro for devices; Brivo, Kisi, or Verkada for badges; Deputy or HiBob for training records
  • Per role and site: the checklist template, the owner of each item, and the lead time before start
Authentication
Owns no credentials. Hire records, directories, devices, and tickets are read, and each account or credential proposed, through the connectors you bind, under the scopes each one holds.

Limits

  • The catalog holds no learning management connector; training items come from Deputy, HiBob, or a per-role list, and Fibric builds an LMS link on request
  • Accounts and credentials are created only through tasks IT and facilities approve; a proposed Okta or Entra ID user is never applied without that answer
  • A hire whose start date moves in the HRIS is re-read, and open tasks get new due dates as proposals, not silent edits
  • Paperwork held inside the HRIS's own onboarding module is tracked as one task; the operator does not read the forms

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Onboarding Checklist ↗

Questions and answers

Who approves what?
The hiring manager approves the checklist and its owners. IT approves each account and device step. Facilities approves each credential. Nothing is created in an identity, access, or ticket system until the owner of that step answers.
What record is left?
The hire id and start date, the checklist as approved, each ticket or task created with its id, each account or credential proposal and who approved it, and the completion time of every item.
Does it create accounts on its own?
No. It drafts the user record with the attributes the hire suggests and hands it to IT. Creating the user, adding group membership, or issuing a card happens once, after approval, and is written to the record.
Ask about Onboarding Checklist

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy