Multiple employments
One employee with multiple employments, and still one account
A nurse who also works evening shifts at another location. A teacher with a post at two schools. In HR those are two employments, and a simple integration turns them into two accounts. Joinly recognises that it is one person.
The short answer
When one employee has multiple employments, they should have one account with the access of all their roles. Joinly recognises in HR that the employments belong to the same person and creates one identity. The roles from each employment count, and when one employment ends, only the access for that role is removed. In the price, that person counts once.
Why two employments lead to two accounts
An HR system thinks in employments, because that is where the contract and the payroll sit. An integration that treats every employment as an employee creates two accounts, two mailboxes and two licences for the same person. The employee has to switch between logins, and your service desk gets the tickets.
In sectors where this is common, such as healthcare, education and hospitality, it is no exception. It is a regular part of the work for an MSP with clients in those sectors.
One person, the access of all their roles
Joinly puts the employments from HR side by side and recognises which ones belong to the same person. That person gets one identity and one account. The roles from each employment count, so the nurse gets the access for both locations.
When one of the employments ends, only the access for that role is removed. The account stays, because the employee still works there. Only when the last employment ends does everything close.
And counted once in the price
Joinly charges per active identity. A person with multiple employments or multiple accounts counts once. For a client in healthcare or education that makes a difference, and you can explain it.
Multiple employments
Frequently asked questions
Does an employee with two employments get two accounts?
No. Joinly recognises that the employments belong to the same person and creates one account, with the access of all their roles.
What happens when one employment ends?
Then only the access for that role is removed. The account stays until the last employment ends.
Does this work with AFAS?
Yes. AFAS has a ready-made integration, as do 77 other HR systems, and multiple employments per person are recognised.
Does someone with multiple employments count twice in the price?
No. Joinly charges per active identity, and a person counts once.
- Joinly for MSPsFor an MSP, every joiner and leaver at a client is a ticket, a checklist and work that is hard to bill for. Joinly picks up those changes from your client's HR system and handles accounts, groups, licences and access automatically. For all your clients, from one login, with each client in its own environment.
- An HR integration per clientOne client uses AFAS, the next Nmbrs and a third a system you have never heard of. For an MSP, that is normal. Joinly connects them all to Microsoft Entra ID or Active Directory in the same way.
- Joiner-mover-leaverJoiner-mover-leaver, JML for short, is the lifecycle of every employee as IT sees it: someone arrives, someone changes, someone goes. It sounds simple, and it is the part of IT management where most access risks start.
- Multiple entities or tenantsA holding company with three operating companies, each with its own records in HR. An education foundation with ten schools. A client that has taken over a competitor and now has two tenants. For an MSP, that is where account management gets complicated. In Joinly you put it side by side in one environment.
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