People ops · Onboarding
Multi-workflowPeople operationsWhat it takes for a new joiner to have everything on day one
A new joiner should arrive to a laptop, working accounts and a manager who knows the plan. Usually they arrive to a ticket that was raised yesterday. This piece follows one hire from accepted offer to their 90-day check-in.
Valnora & Elric team5 min read
Amara accepts an offer as a senior financial analyst on a Thursday afternoon. Her start date is five weeks out. In many companies, what happens next depends on a recruiter remembering to email IT, IT remembering to order a laptop, and a manager remembering that a new person arrives on Monday. Amara's first day then goes on borrowed equipment and a list of passwords that do not work yet.
None of these steps is hard. They are just spread across four teams and five tools. This piece follows Amara from the accepted offer to her 90-day check-in, through four workflows built in Agent Serve, with a person approving each step that grants access or speaks for the company.
Four workflows from accepted offer to day 90
Workflow 1 · Start
- 01Offer acceptedGreenhouse or Ashby hire events, or a morning check of new hires in Workday.
- 02Onboarding tableOne row per joiner: role, team, manager, start date, location and task status.
Workflow 2 · Accounts and laptop
- 03Access by roleA role-to-groups table says which apps and groups each role gets.
- 04IT approvesA Human in the loop step shows IT the exact accounts and groups requested.
- 05Okta or Microsoft EntraThe user is created and added to the approved groups.
- 06Laptop ticketA request in Jira Service Management with model, shipping address and date.
Workflows 3 and 4 · Welcome and check-ins
- 07Handbook and team notesThe welcome pack draws on the handbook, the team page and first-week plans.
- 08HR approves the packThe pack is drafted to a document and sent only after HR approves it.
- 0930-60-90 check-insCalendar events for the manager and joiner, each with a short agenda.
The accepted offer starts everything
Hiring decisions belong to people, and nothing here touches them. The work starts after the offer is accepted.
If the company recruits in Greenhouse or Ashby, their hire events start the first workflow directly. For Workday, a Schedule trigger checks each morning for new hires added since the last run. Either way, the workflow writes one row to an onboarding table in Tables: Amara's name, role, team, manager, start date and office, with a status column for each task that follows.
The table is the shared view. HR, IT and the hiring manager all see the same row, and each later workflow starts when the row is created or updated.
Accounts, with IT in the loop
The second workflow works out what Amara needs. A role-to-groups table, kept by IT, says that a senior financial analyst in FP&A gets the Finance and FP&A groups in Okta, plus the all-staff groups. A company on Microsoft Entra keeps the same mapping against Entra groups and licences.
Before anything is created, a Human in the loop block pauses the run and shows the IT approver exactly what will happen: the user, the groups, the apps. If the role is new or unusual, IT edits the list or rejects it with a note. Once approved, the workflow creates the user in Okta or Entra and adds the groups. The approval and the result are written to the run log, which is the evidence a later user access review will ask for.
A laptop that ships in time
The same workflow raises a request in Jira Service Management for a laptop, using the request type IT already uses. It fills in the standard build for the role, the start date and the office or home address from the onboarding row, and sets the date the laptop must ship by, a week before the start date. The request number goes back to the onboarding table.
IT works the request in Jira Service Management as usual. The workflow does not order hardware or choose a supplier; it only makes sure the request exists early enough, with the details right.
A welcome pack a person signs off
The third workflow prepares Amara's welcome pack two weeks before she starts. An agent block searches the employee handbook and the FP&A team's onboarding notes in a Knowledge Base and drafts a short document: where to go on day one, who to meet in week one, which systems she will use, and the reading her manager suggested.
The draft is saved to Files and an HR partner approves it through a Human in the loop step, editing anything that does not sound right. Only then does the workflow email it to Amara's personal address from the HR inbox. Nothing goes to a joiner without an approval.
What the solution produces
Onboarding record for one joiner (illustrative)
Record- Joiner
- Amara O. · Senior financial analyst · FP&A
- Start date
- Monday 2 November · London office
- Manager
- Head of FP&A
- Accounts
- Approved by IT on 19 Oct. Created in Okta with Finance, FP&A and All staff groups.
- Laptop
- JSM request IT-2291 · 14-inch standard build · ships 28 Oct
- Welcome pack
- Drafted 20 Oct · waiting for HR approval
- Check-ins
- Booked for 2 Dec, 4 Jan and 1 Feb with the manager
Check-ins at 30, 60 and 90 days
The fourth workflow runs on Amara's start date. It books three calendar events in Google Calendar or Outlook for her and her manager, at roughly 30, 60 and 90 days, each with a short agenda drawn from the team's onboarding notes: what good looks like by then, what to review, what support she needs.
A day before each check-in, the workflow sends the manager a reminder in Slack or Teams with the agenda. After the 90-day meeting, the onboarding row is marked complete. The workflow does not score Amara or record performance notes. Those conversations stay between her and her manager.
Personal data and access
Onboarding records carry personal details: home addresses, phone numbers, sometimes right-to-work documents. Keep the minimum on the onboarding row, and leave salary and documents in the HR system where they already live. PII redaction can mask personal data in logs and block outputs, and row-level access lets each manager see only their own joiners.
Controls and governance
Approvals before action
Relays never send email or book meetings without an approval, under any autonomy setting. An approval covers the exact payload the reviewer saw and expires if nobody decides.
Run logs
Every workflow run records each block’s inputs, outputs and errors, so a reviewer can trace how a result was reached.
Audit trail
Proposals, approvals, declines and executed actions are written to the workspace audit log, which admins can export.
PII detection
A Guardrails block detects personal data and blocks or masks it before text reaches the next step.
Row-level access
Row-level policies narrow what each person sees in tables, dashboards, exports and scheduled reports.
Deployed versions
Workflows run from a deployed version, so a change is reviewed before it reaches production runs.
More on how Agent Serve handles access, data and audit on the security page.
Where to start
Begin with one team and one source: hires from Greenhouse into finance, for example. Run the account workflow with IT approving every request for a month, and compare what was granted with what the joiner actually needed in week one. Adjust the role mapping before adding more teams. Workflows run from a deployed version, so each change to the mapping or the pack is reviewed before the next joiner sees it.
For approving changes to the mapping and other access rules over time, see change management approvals.
Questions teams ask
Does any of this decide who gets hired?
No. Everything starts after a person has made the hiring decision and the candidate has accepted. The workflows only handle the logistics that follow.
Why does IT approve accounts that follow a fixed role mapping?
Role mappings drift, and a hire into an unusual role may match the wrong groups. A short approval step lets IT catch that before access exists, and it leaves a record of who approved what for later access reviews.
What you need
- Greenhouse, Ashby or Workday connected, with the role, manager, start date and location on each hire
- Okta or Microsoft Entra connected, and a table that maps each role to its groups and apps
- A Jira Service Management project and request type for new laptops
- Your employee handbook and team onboarding notes in a Knowledge Base
- A named IT approver for accounts and an HR approver for the welcome pack
- Google Calendar or Outlook connected for booking check-ins