How does Joinly sync Talentech to Active Directory?

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

1. Joiner. HR confirms the hire in Talentech and the record lands in HR master data. Joinly reads it, determines the role from department, job title and location, 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 confirmed start date, not the preboarding journey.

2. Mover. When someone changes department, role or location, 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 leaving date, Joinly instructs the agent to disable the AD account and optionally move it to a disabled-users OU, so nothing stays active after someone has left.

Example: A national logistics operator runs Talentech and an on-premise AD across four depots. It hires a warehouse planner with a start date next Monday, who first goes through preboarding the week before. Joinly ignores the preboarding record and waits for the confirmed HR master-data record; on Monday morning the AD Agent creates the user in the Depot-North > Operations OU, sets the sAMAccountName to a unique pattern, and adds the Warehouse-Operations group. When the planner later moves to dispatch, the agent moves the object to the new OU and swaps the groups the same day.

What manual AD account management costs

Without automation, every account starts as a Talentech hand-off that an admin works through in Active Directory Users and Computers by hand — creating the object, choosing the OU, building the sAMAccountName, adding groups. Because Talentech has no native AD provisioning connector, teams usually script against the REST API or run a middleware job that offers limited mapping, no role-to-group logic and no idea which module holds the real employee, so the decisions still fall to people.

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

• Permissions that don’t keep up (privilege creep). When movers change department or location, 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 long after someone has left the organisation.

Joinly vs. the Entra provisioning agent for AD

Talentech has no native AD provisioning connector, so the alternative is Microsoft’s Entra provisioning agent fed by a custom API-driven build, or a hand-written script against the Talentech REST API. Either way it stops short of the part that actually decides access. Here’s how Joinly compares for a Talentech HR-driven AD setup.

Watch-outs when connecting Talentech to Active Directory

A few 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. Joinly builds it from your rules with a fallback pattern, so duplicate names never produce a collision or a truncated, unreadable login.

• Read the right module before you place the OU. Talentech is a suite: the ATS holds candidates and the onboarding module holds preboarding journeys, but only the HR master data is a confirmed employee. Joinly reads the HR record, so a candidate or an unfinished preboarding journey never gets an AD object created.

• OU placement from Talentech attributes. Department, role and location 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.

• Preboarding starts before day one. Talentech begins preboarding before the first working day. Joinly reads the confirmed start date and has the agent create the account on the right day, not the moment preboarding opens.

• 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 Talentech 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 national logistics operator with around 1,800 employees across four depots and a head office, running Talentech for recruitment, onboarding and its HR record while still living in an on-premise Active Directory for its warehouse and transport-management systems. Every new driver, planner or picker starts as a Talentech onboarding hand-off that IT processes by hand in AD — creating the object, choosing the OU, building the login, adding groups. With seasonal peaks and constant internal moves the queue never empties, and new joiners wait until day two or three for their account.

Connect Talentech to Active Directory with Joinly and that work disappears. The Joinly AD Agent reads the confirmed HR master-data record and 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 leaving date with a 30-day grace window — all driven by the HR change in Talentech, and never by a candidate or an unfinished preboarding journey.

“An account is simply ready in the right OU when the driver clocks in, transfers move themselves, and candidates never leak into AD because Joinly only reads the confirmed HR record.” — Head of IT, logistics operator

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