Tabijn uses HR2Day as the source for Entra ID, and Entra ID as the source for ESIS. New staff get an account automatically, leavers are deactivated, and in ESIS everyone gets access to the schools where they work.
Connected systems: HR2Day → Entra ID → ESIS
Category: Identity and access management, user management in applications
The situation
Tabijn is a primary school board with several schools. Personnel records are kept in HR2Day. Teachers and other staff need a Microsoft account and a user in ESIS, the pupil administration system. In ESIS, access depends on the school where someone works.
What the integration does
HR2Day to Entra ID
- Joiners. A new employee gets an account in Entra ID. The employee and IT are notified.
- Movers. Changes in HR2Day are passed on to the account.
- Leavers. When someone leaves, the account is deactivated and IT is notified.
- Consistent job titles. Job titles are the same everywhere in Entra ID, even when they carry an addition in HR2Day.
- No duplicate accounts. When an account already exists, IT gets a notification instead of a second account.
Entra ID to ESIS
- Joiners. Active staff are created in ESIS and sign in with their Microsoft account.
- Schools. The employee's location decides which schools they can access. When the location changes, access changes with it.
- Leavers. After the leave date, access to ESIS is removed.
- Updates. Changes in Entra ID in the meantime are passed on to ESIS.
What it changed
A new teacher has an account and access to ESIS for their own school on the first working day. When someone leaves, account and access close without anyone having to remember. HR2Day remains the only place where HR enters anything.
Systems
- Source: HR2Day
- Identity: Microsoft Entra ID
- Application: ESIS
- Direction: HR2Day → Entra ID → ESIS
