Education
21 schools, one way of handling accounts
A primary education board handles the accounts of more than five hundred employees centrally, while every school keeps its own structure. The start of the school year no longer costs weeks of manual work.

- employees
- over 500employees
- schools under one board
- 21schools under one board
- changes a month, handled automatically
- around 45changes a month, handled automatically
One peak a year, and it fell at exactly the wrong moment
A school board has a rhythm few other organisations have. It is quiet all year, and then summer arrives. Around the start of the school year a group of new teachers joins, people move between schools, colleagues retire and supply teachers start, all in the same few weeks.
At this board, with twenty-one schools and more than five hundred employees, all that work landed on a small IT team, precisely when the schools themselves were also starting up and every teacher wanted to be in the system on day one. Whoever did not get their turn in August began the school year on a colleague's account.
What they wanted: handled centrally, different per school
The board wanted to handle accounts centrally, from the HR system, without the schools having to become the same. Every school has its own teams, its own shared folders and its own way of working, and that had to stay. What had to be central was the process: whoever joins gets an account, whoever moves school gets the access of the new school, whoever leaves loses everything.
In August nobody has time to create accounts. So the system does it.
What was built: school and role determine the access
Joinly reads the HR system and translates school and role into the accounts and groups that belong with them. A teacher at school A lands in the groups and Teams of school A; a head gets what a head needs; a supply teacher working at three schools gets the access of all three. The structure per school is set down the way the board wants it, and applied by the system.
A move to another school is one change in the HR system. Joinly adds the new school and removes the old one. And on the end date of a contract the account closes, even when there are eighty of them at once in August.

Today: a calm start to the school year
The start of the school year no longer costs weeks of manual work. Whatever is entered in the HR system is ready on the first school day, for all twenty-one schools at once. Through the year Joinly handles around forty-five changes a month without anyone looking at it.
Every school keeps its own structure, and the board has one overview of who has which access at which school. That overview is there in September too, when everyone is too busy to make it.
What you can count on
- No vendor lock-inYour identities and your configuration stay yours.
- Your data out whenever you wantYou can export your data at any time.
- Standard SLAOur standard SLA is available on request.
- Support during implementationOur specialists set it up together with you.
- ISO 27001 certifiedInformation security to an internationally recognised standard.
Customer stories
More customer stories
Organisations with a similar question, in a different sector.

Public sector
Access that follows the job, in an organisation that accounts for itself
more than 600 employees
Read the story
Public sector
Public money, demonstrably managed access
around 210 employees
Read the story
Healthcare
750+ care workers with the right access, with no waiting
750+ employees under management
Read the story
Want to see what this means for your organisation?
Book a 30-minute demo. We walk through your own situation: which HR system you use, which systems need to follow and what can be automated first.
Book a demo