A new starter set up from the role list, not from a colleague’s access.
The agent reads the onboarding ticket, creates the accounts the role needs and tells the team. Access outside the role list waits for the hiring manager.
DesignedThe steps and approvals are designed. It has not run yet.
A decade in defence and aerospace. In government procurement since 2016. The same technology since 2019, validated in US DoD and Canadian DND programs.
An AI agent for employee onboarding does the setup work between the offer and the first day: the account, the mailbox, the calendar, the standard access for the role and the note to the team. Each piece lives in a different system, and each one is a place where a starter gets too little access to work or more access than the role allows.
This workflow is designed. The steps below are how we build it in a pilot. It has not run in the sandbox yet.
What a person still decides
- The role, the start date and the manager. HR sets them on the ticket.
- What the standard access list for each role contains.
- Any access beyond that list, case by case.
The rest of the library is on the workflows page. The guarantees say what each control covers and where it stops.
One new starter, from the ticket to the first-day note.
The role and the systems are examples. Each step names the system, who approves and the line written to the record.
- 01Ticketing
Take the onboarding ticket and receive a credential for this starter only. It expires when setup ends.
- Who approves
- No approval on this step
- On the record
- credential issued · one starter
- 02Ticketing
Read the ticket: name, role, start date and manager.
- Who approves
- No approval on this step
- On the record
- read-ticket · allowed
- 03Documents
Read the standard access list for the role.
- Who approves
- No approval on this step
- On the record
- read-role-list · allowed
- 04Office suite
Create the account, the mailbox and the calendar.
- Who approves
- No approval on this step
- On the record
- create-account · allowed
- 05In-house tool
Read the starter’s salary and bank details in the HR system to fill the welcome pack. Pay data is outside the permission for setup, so the step is refused.
- Who approves
- No approval on this step
- On the record
- read-pay-data · refused · outside permission
- 06Accounting
Grant read access to the accounting system, which is not on the role list. The step waits until the hiring manager approves it.
- Who approves
- Hiring manager
- On the record
- grant-accounting-read · approved by hiring manager
- 07Email
Send the first-day note to the team. The starter’s home address and personal phone number are taken out before it leaves.
- Who approves
- No approval on this step
- On the record
- send-team-note · redacted · personal details
- 08Ticketing
Update the ticket with what was set up, and close the job.
- Who approves
- No approval on this step
- On the record
- setup complete · credential closed
The systems, by type
We name systems by type. Yours are named in the assessment.
Ticketing
Holds the onboarding request from HR, and the list of what was set up at the end.
Documents
The access list for each role. The agent reads it. Your people write it.
Office suite
The account, the mailbox and the calendar the starter needs on day one.
In-house tool
Your HR system and your own tools. The agent grants only what the role list names and may not read pay data.
Accounting
An example of a system outside the standard list. Access to it needs a decision.
Carries the first-day note to the team, checked before it leaves.
The approval, the refusal, the record
- A person approves: Grant read access to the accounting system, which is not on the role list. The step waits until the hiring manager approves it.Access outside the role list is a decision about what one person may see, so the hiring manager makes it and the agent waits.
- Refused: Read the starter’s salary and bank details in the HR system to fill the welcome pack. Pay data is outside the permission for setup, so the step is refused.Setting up accounts needs the role and the start date, not pay, so this job has no right to read pay data.
- On the recordEach account created, each grant with its source in the role list, the refused read of pay data, the approval with a name, and the text removed from the team note.
What goes on the record
- credential issued · one starter
- read-ticket · allowed
- read-role-list · allowed
- create-account · allowed
- grant-accounting-read · approved by hiring manager
- setup complete · credential closed
One record per step, as designed. This workflow has not run yet.
What it does not do
- It does not hire, set pay or issue contracts. HR does.
- It does not write the role lists. It follows them, so a wrong list gives wrong access.
- It does not remove access when a person leaves. That is a separate workflow.
Questions and answers
Tell us about one workflow.
We will say whether an agent should do it, and what the first step costs.
A senior member of the team replies within two business days.