For managers and teams
Every manager and every team sees its part of onboarding
Journey is employee onboarding for SharePoint that iomer builds for your organization and installs in your tenant. Managers see who on their team is behind. IT, safety and facilities see every new hire against every task they own.
What changes for managers and teams
Nobody chases status by email
The whole team at a glance
Every direct report’s progress, from the manager field in Entra ID, with overdue items flagged.
Act for a report, on the record
Remind, extend a due date, record a task or a paper acknowledgement. The person is told what you did.
Every task your team owns
A completion matrix of every new hire against every task in your stream, and your team’s tasks ready to do.
Approvals with the evidence
Access reviews and competency sign-offs routed to you, showing what the new hire wrote.
The manager’s view
Your team, from the manager field in Microsoft 365
My team lists your direct reports with their progress and overdue items, and shows anyone with a hire date but no journey yet.
The stream owner’s view
Every new hire against every task in your stream
IT, safety, HR and facilities each see their own stream: who’s complete, who’s waiting on approval, and the tasks their team needs to do next.
Examples
What it looks like in a working week
Set in an example utility of about 1,800 staff. Names and figures are illustrative.
ExampleThree people behind, seen on Monday morning
A commercial team manager has four people in onboarding, one starting next week and two more with hire dates set in Entra ID but no journey yet.
Without Journey
He tracks them from memory and his inbox. He doesn't know that one is two tasks overdue on site safety, and nobody has told him the two new hires have no onboarding plan.
With Journey
My team lists his direct reports from the Entra ID manager attribute, each with progress, overdue and in-approval counts. He sees Aisha with 2 overdue, reminds her from her journey, extends one due date, and uses Assign a journey for Jordan, who has a hire date but no journey yet. Journey tells each person what he did.
Managers see who's behind before it becomes a problem, and every action they take for someone is on the record and visible to that person.
ExampleA competency sign-off with the evidence in front of him
A field technician has finished her site induction and two supervised visits and submits her safety competency sign-off.
Without Journey
Today it's a paper form signed by the supervisor and posted to the safety office, which signs it weeks later. The dates rarely line up with when she actually started working alone.
With Journey
The sign-off arrives in David's Approvals with what Aisha wrote (induction date, PPE check, supervised visits). The approval shows level 1 is the manager, from Entra ID, and level 2 is the Safety Officers approver list. He approves with a comment; Journey checks before the decision and passes it to level 2.
Multi-level approvals follow the org chart, carry the joiner's own evidence, and keep a dated trail of each decision.
ExampleThe laptop is ready on day one
A remote marketing designer starts on Monday. The laptop has to be imaged, licensed and shipped by Friday.
Without Journey
The service desk heard about her from a ticket People Ops raised two days before her start date. The laptop arrives on Wednesday of week one.
With Journey
Laptop and accounts ready is the first task in the IT & Security stream, due on day 0 and owned by the stream owner's team. It appears in IT's Tasks for you as soon as her journey is assigned, which a rule does when she's added to Entra ID, often weeks ahead. The completion matrix shows her row as 0% with the task open.
IT sees new hires as soon as they're assigned, not when someone remembers to raise a ticket.
ExampleEvery new field worker, every safety task, one screen
Before the safety certification audit, the safety officer needs to show which new field workers have completed orientation, PPE and competency sign-off.
Without Journey
She spends three days reconciling district binders against the HR new-hire list, and still can't vouch for the dates.
With Journey
The stream monitor's matrix for Site Safety shows each assigned worker against each task, with complete, in progress, awaiting approval, overdue and not-yet-available marked. Overdue items are listed under the matrix. Reports filter the same records by location and start date, and the CSV export lists the filters it used.
Safety completion is visible live, by person and task, without reconciling paper.
See it the way your managers and teams would
Watch the 40-second tour of a policy acknowledgement, an approval and a stream, or book a walkthrough and bring a manager to drive it.