For HR and IT teams

Every new starter has a work account on day one.

Every new starter in HiBob gets a Microsoft 365 account with their name, work email and job title. Giving access is HR's decision; everything else runs on its own, with nothing typed twice and no personal details copied.

Free sandboxTemplate ready to runSwap in your own apps

Watch it run: New-hire onboardingThe workflow running in Nexra, from the first app to the record it leaves behind.
The problem

HR adds them. IT types them again.

A new starter is added in the HR system, then someone emails IT, who types the same details again. Day one starts with a missing login.

  • HiBob
  • Microsoft 365 (a person approves this step)

Today

HR adds a new starter, then emails IT, who types the same details again.

With Nexra

Every new starter in HiBob gets a Microsoft 365 account with their name, work email and job title, ready to switch on.

How it runs

Connect. Govern. Prove.

These are the exact steps the sandbox template runs. Routine runs go through on their own; only the exceptions you set wait for a person.

Connected

Apps, APIs, providers, and workflows.

HiBob to Microsoft 365, on its own.

A new starter in HiBob starts the flow. Nexra prepares their Microsoft 365 account, switched off until IT is ready, with only their name, work email and job title. Everything else runs on its own.

  1. HiBob · Read the new starteremployees.searchRuns on its own
  2. Microsoft 365 · Create the work accountusers.createException: Every new account needs HR: an access decisionMaker-checker

Approved

Permissions, approvals, limits, and secure credentials.

Access is HR's decision.

Every new account needs HR, because giving someone access is a decision, not a data copy. HR approves the account; everything else runs on its own, and no pay, bank or personal details are copied.

Approval · HRMaker-checker

Create a work account for a new starter

Prepared by
New starter flow
Account
Name, work email and job title only
Rule
Every new account needs HR
Expires
in 58 minutes, single use

Proven

Testing, reconciliation, logs, and evidence.

Every account, accounted for.

Who approved each account, when, and what was created all join the evidence chain, ready for your next access review.

Evidence · new starter

  • Approved by HR at 08:30:12, under "Every new account needs HR"
  • Microsoft 365 account created, switched off until day one
  • No pay, bank or personal details copied

Example workflow, runnable in the sandbox. Names, amounts and times are illustrative.

Open by default

Use the apps you already run.

Same flow, same approvals, same evidence. Swap any step for another connector, or your own system with a REST or OpenAPI interface.

Give your next starter a login on day one.

Install the template in your sandbox and watch a test starter become a work account, with HR's access decision and the record to prove it.