Skip to main content
Joinly by KoppelHet

Onboarding and offboarding

Onboarding and offboarding at all your clients, automatically from HR

An onboarding checklist per client and an offboarding ticket that arrives too late: for most MSPs, that is the work that comes back most often. With Joinly it starts as soon as your client records an employee in HR, and it follows the whole lifecycle.

The short answer

Automating onboarding and offboarding means your client's HR system starts the process. When your client records a new employee, Joinly creates the account in Microsoft Entra ID or Active Directory, with the right groups, licence and welcome email. When someone leaves, their account, sessions and licence are closed on their last day. This is known as the joiner-mover-leaver lifecycle.

A checklist is only as good as the message that starts it

Every MSP has an onboarding checklist, and it looks slightly different at every client. The checklist itself is not the problem. The problem is that it only starts when someone at your client remembers to raise a ticket, with the right role, department and start date.

Offboarding is where that matters most. An account left open after someone leaves is the risk that surfaces first in an audit or an incident. And the middle of the lifecycle, the change of role, usually never arrives as a ticket at all. That is where rights quietly pile up.

Joiners: everything ready before the first working day

With Joinly, the record in HR is the signal. As soon as your client records a new employee, Joinly creates the account following that client's naming convention, puts the employee in the groups and Teams that belong to their role, assigns the licence and sends the welcome email, from your client's own mail environment if you prefer.

If a laptop or phone needs to be ready too, Joinly creates a task in the service desk, in TOPdesk or Freshservice. So your team knows in time what needs doing, without anyone at your client having to think of it.

Het lifecycle-overzicht in Joinly: accounts die elke HR-mutatie automatisch volgen

Movers: access that follows the role

When someone changes role or department, Joinly adjusts their access based on roles. What belongs to the new role is added, what belonged to the old one is removed. No ticket is needed and nothing is left behind.

That is the part of the lifecycle a checklist almost never gets right, and the part where an access review later finds the most differences.

Leavers: closed on the last day, with nothing forgotten

When HR has an end date, the account, sessions and licence are closed on that day and the mailbox is dealt with the way you set out for that client. The licence is freed up for the next employee.

Accounts that do not come from HR, such as contractors, external staff and guest accounts, get an owner and an end date in Joinly. That way they follow the same lifecycle and close on their own.

What happens, moment by moment

The whole lifecycle of an employee at your client, without a ticket.

Joiner
What Joinly does: Account, groups, Teams, licence, welcome email and a task for hardware
The signal: New employee in HR
Mover
What Joinly does: Access from the old role removed, from the new role added
The signal: Role or department changed in HR
Leaver
What Joinly does: Account, sessions and licence closed, mailbox dealt with
The signal: End date in HR
Contractors and external staff
What Joinly does: Account with an owner and an end date
The signal: Request or workflow

Onboarding and offboarding

Frequently asked questions

  • What is joiner-mover-leaver?

    Joiner-mover-leaver (JML) is the name for the lifecycle of an employee: joining, moving and leaving. A JML process sets out, at each of those three moments, which accounts and which access someone gains or loses.

  • What is the difference between an onboarding checklist and automated onboarding?

    A checklist describes what needs to happen and waits for someone to start it. With automated onboarding, the change in HR starts the process, and Joinly carries out the steps and records them in the audit log.

  • Can I have different rules per client?

    Yes. The naming convention, when an account closes, which groups belong to which role and what goes in the welcome email are all set per client. Whatever is the same for all your clients is your standard.

  • Does this also work with an on-premises Active Directory?

    Yes. At a client with an on-premises Active Directory, the Joinly Agent runs with outbound traffic only. Hybrid Exchange works the same way.

  • Does Joinly also create a ticket in our service desk?

    Yes, for whatever a person needs to do, such as getting a laptop ready. Joinly works with TOPdesk and Freshservice. Get in touch if you use a different service desk.

  • Does this also work for contractors and external staff?

    Yes. Accounts that do not come from HR get an owner and an end date, and close on their own when it passes.

Account management for your clients as a standard service?

In an introduction we walk through how Joinly would work for your clients: which HR systems, which environments and where you want to start. We agree the terms of a partnership in the same conversation.

Book an introduction