enaudo
Employee onboarding in one shared case
Onboarding can be automated by turning confirmed contract and start details into a shared set of tasks. HR, IT and the line manager work from the same status. Access is prepared, while activation and outgoing messages wait for the responsible person to approve them.
When this workflow helps
This supporting HR workflow helps when equipment orders, employee records and IT requests live in separate lists. Handoffs are often the weak point: a changed start date does not reach everyone, or a missing account has no owner. A shared case connects those tasks without requiring a large HR platform.
The workflow, step by step
-
Start details confirmedDone
-
Check documentsDone
Contract and personal details are in place.
-
Prepare and approve accessDone
A tick starts the preparation automatically. Approval stays with you.
-
Plan the introductionDone
When on the first day?
-
Welcome messageDone
Ready for the first day
Access for Mara Beispiel
A tick starts the preparation: account, access and invitation run automatically. Activation, sending and withdrawing access need your approval.
- Create account open
- Assign access open
- Prepare invitation open
- Create account open
- Assign access open
- Prepare invitation open
- Create account open
- Assign access open
- Prepare invitation open
- Create account open
- Assign access open
- Prepare invitation open
First day, 1 June
Try it: tick tools under access and watch the preparation run by itself. Unticking reverts the run. You approve sending and activation yourself. Nothing is sent or saved and no access is created.
Examples built for this website with invented data: no client systems, no references, no AI running. The scope is defined per project.
-
Confirm start details
Check contract status, start date, role and line manager, then assign a unique case reference.
-
Assign tasks
Create role-based tasks before, on and after the first day, each with an owner and due date.
-
Prepare access
Propose required accounts and permissions. Keep prepared accounts inactive where the target system supports this.
-
Draft welcome information
Use confirmed practical details to prepare a message covering contacts and the first working day.
-
Approve activation
ApprovalResponsible people check permissions and recipients, then explicitly approve activation and sending.
-
Check the outcome
Confirm completed actions and keep missing equipment, access and other outstanding tasks visible.
Data, systems and people involved
- Reliable employee details: name, work contact details, contract status, start date, role and responsible manager.
- A maintained task and access matrix specifying equipment, applications and approvals for each role.
- An HR system or approved list as the source, a task tracker and checked connections to the accounts actually required.
- HR confirms the start, the manager confirms business needs and IT checks technical permissions. Access to employee data is limited to the roles that need it.
What runs automatically and who decides
Case creation, deadlines, reminders and task reconciliation can run automatically. AI may draft a welcome message from confirmed information. Contract decisions, additional privileges and access activation stay with named people. If an application has no safe inactive account state, account creation is also held until approval.
Exceptions, errors and stopping points
- The start date or role changes: Recalculate tasks and deadlines. Review existing approvals affected by new permissions or sending dates.
- The contract is unconfirmed or the start is cancelled: Stop activation and messages. Refer prepared accounts and orders for a human decision.
- An account already exists or a system is unavailable: Check the actual state and continue only missing steps. Do not create a second identity or duplicate invitation.
A useful first scope and acceptance check
A useful first scope is one role with a manageable set of applications. Acceptance covers a normal start, a postponed start and a cancelled case using suitable sample data. Every task must have an owner, no access may activate before approval, and errors and outstanding work must remain visible.
Related workflows and implementation
Frequently asked questions
Do we need Personio or another HR platform?
An HR platform can provide confirmed start details. A list with clear ownership can also be a starting point. What matters is a reliable source, a role matrix and checked access to the target systems.
Can preparation begin before the first working day?
Yes, once the agreed contract status is confirmed. Equipment and tasks can be prepared. The timing and approval of each access activation are defined separately.
What happens when the start date changes?
The case keeps its identity. Due dates and scheduled messages are updated, while effects on prepared accounts and existing approvals are presented for review.
Does onboarding require AI?
No. Tasks, permissions and approvals follow explicit rules. AI is optional for drafting text and receives only the data agreed for that purpose.
If a process is eating time in your team, describe it. We will say honestly whether automation is worth it.