How does Joinly sync Loket to Active Directory?

Joinly reads each HR change in Loket in the cloud through the REST API, then hands the action to the Joinly AD Agent inside your network, which makes the change in Active Directory. Loket holds the authoritative werknemer and dienstverband record; the agent is the only component that touches your domain.

1. Joiner. The salarisadministrateur enters the new werknemer and dienstverband in Loket. Joinly reads the new records, determines the role from department, function and werkgever, and instructs the AD Agent to create the user in the correct OU, build the sAMAccountName and UPN from your rules, and add the right security groups — timed to the start date of the dienstverband.

2. Mover. When someone changes function, department or werkgever, Joinly tells the agent to move the user to the matching OU, swap security-group membership and update attributes. Access that no longer fits the new position is removed, so permissions stay aligned with the actual job.

3. Leaver. On the end date of the dienstverband, Joinly instructs the agent to disable the AD account and optionally move it to a disabled-users OU. Because a persoon can hold more than one dienstverband, an account is only disabled when the last active employment ends.

Example: A hospitality business runs Loket for payroll and an on-premise AD across a hotel and two restaurants. It hires a front-office employee with a start date next Monday. Joinly reads the new dienstverband through the API, and on Monday morning the AD Agent creates the user in the Hotel > FrontOffice OU, sets the sAMAccountName to a unique pattern, and adds the Reception group. When that employee later picks up shifts at one of the restaurants under a second dienstverband, the agent keeps a single AD object and adds the extra group rather than creating a duplicate.

What manual AD account management costs

Without automation, every account starts as an email from the salarisadministratie that an admin works through in Active Directory Users and Computers by hand — creating the object, choosing the OU, building the sAMAccountName, adding groups. Loket exposes a clean REST API, but on its own it offers no OU logic, no role-to-group mapping and no UPN rules, so the decisions still fall to people.

• Onboarding delays. New joiners wait for an AD account and group access while a request sits in a queue, losing productive days in their first week.

• Permissions that don’t keep up (privilege creep). When movers change function or werkgever, old security-group membership often stays attached, so people accumulate rights they no longer need.

• Forgotten offboarding. Accounts that aren’t disabled on time are a security and audit risk — and with multiple dienstverbanden it is easy to disable an account while another contract is still active.

Joinly vs. a scripted Loket-to-AD integration

Loket’s REST API is a clean source, but writing to on-premise AD from it means building and maintaining your own scripts or an iPaaS flow — and that stops short of the part that actually decides access. Here’s how the two compare for a Loket-driven AD setup.

Watch-outs when connecting Loket to Active Directory

A few Loket-specific details decide whether this connection stays reliable at scale.

• sAMAccountName uniqueness and length. AD limits the sAMAccountName to 20 characters and it must be unique across the domain. Loket doesn’t supply one, so Joinly builds it from your rules with a fallback pattern — duplicate names never produce a collision or a truncated, unreadable login.

• OU placement from Loket structure. Werkgever, administratie and department don’t map one-to-one to your OU structure. Joinly builds explicit rules that place each user — and move them on a transfer — into the correct OU.

• Accountant-administered provider structure. One administratiekantoor (provider) in Loket can span several client werkgevers. Joinly pins the connection to the werkgever(s) and administratie(s) that belong to your domain, so only the intended population is provisioned to AD.

• Multiple dienstverbanden per person. A single persoon can hold more than one dienstverband. Joinly applies rules to keep a single, stable AD object driven by the primary employment, so a second contract adds groups rather than creating a duplicate account.

• Service-account permissions. The agent acts under a service account with delegated rights. Joinly works with least-privilege delegation scoped to the target OUs, so the agent can create, move and disable users without domain-admin rights.

Joinly handles each of these by default with custom mapping and transformation.

Always audit-ready

Every account action the Joinly AD Agent performs is logged in the Joinly cloud: who was affected, when it happened, which OU and groups changed and which Loket change triggered it. For NIS2 that matters directly: access can be traced back to an authorised HR source rather than an ad-hoc request. Joinly is ISO 27001 certified, runs in an EU data centre in Amsterdam, applies least-privilege by default, and is built to meet NIS2 and ISO 27001.

Example case

Take a hospitality business with around 180 staff across a hotel and two restaurants, payrolled in Loket but still living in an on-premise Active Directory for its front-office, reservations and kitchen systems. Every new receptionist, server or kitchen hand starts as an email from the salarisadministratie that IT processes by hand in AD — creating the object, choosing the OU, building the login, adding groups. With high seasonal turnover and staff picking up shifts across venues under a second dienstverband, the queue never empties and new joiners often wait until their second shift for an account.

Connect Loket to Active Directory with Joinly and that work disappears. The Joinly AD Agent creates each user in the right OU on the start date, builds a unique sAMAccountName, adds the correct security groups, moves people on a transfer and disables accounts on the end date of the dienstverband with a 30-day grace window — all driven by the HR change in Loket, and keeping one AD object even when someone works across two venues.

“An account is simply ready in the right OU when the new server walks in, people who work across venues keep one login, and we can show the auditor exactly which Loket change created every bit of access.” — Head of IT, hospitality business

The outcome this setup is designed for: onboarding drops from days to zero touch, duplicate accounts from second contracts are eliminated, and the team can walk into its next NIS2 assessment with a complete, source-backed audit trail.