How does Joinly sync TeamSystem to Active Directory?

Joinly reads each HR change in TeamSystem HR in the cloud, then hands the action to the Joinly AD Agent inside your network, which makes the change in Active Directory. The TeamSystem anagrafica holds the authoritative employment record; the agent is the only component that touches your domain.

1. Joiner. HR completes the hire in TeamSystem HR. Joinly reads the new anagrafica, determines the role from unità organizzativa, mansione and centro di costo, 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.

2. Mover. When someone changes mansione, unità organizzativa or sede, 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 termination date, Joinly instructs the agent to disable the AD account and optionally move it to a disabled-users OU. The matricola keeps the right object matched, so the correct account is always the one retired.

Example: A distribution and wholesale company runs TeamSystem HR and an on-premise AD across three branches. It hires a warehouse operative assigned to the Bologna sede and the Logistics unità organizzativa. Joinly reads the new anagrafica, and the AD Agent creates the user in the Bologna > Logistics OU, sets a unique sAMAccountName transliterated from an accented surname, and adds the Warehouse group. When the operative later moves to dispatch, the agent moves the object to the new OU and swaps the groups the same day, keyed on the matricola.

What manual AD account management costs

Without automation, every account starts as a TeamSystem ticket that an admin works through in Active Directory Users and Computers by hand — creating the object, choosing the OU, building the sAMAccountName, adding groups. Microsoft’s Entra provisioning agent can push data to on-premise AD, but it offers limited mapping, no role-to-group logic and leaves username transformation to people, so the decisions still fall to staff.

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

• Permissions that don’t keep up (privilege creep). When movers change mansione or unità organizzativa, 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 every dormant object is another way in for an attacker.

Joinly vs. the Entra provisioning agent for AD

Microsoft’s Entra provisioning agent can write data to on-premise AD, but it stops short of the part that actually decides access. Here’s how the two compare for a TeamSystem HR-driven AD setup.

Watch-outs when connecting TeamSystem to Active Directory

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

• sAMAccountName uniqueness, length and accented names. AD limits the sAMAccountName to 20 characters and it must be unique across the domain, while TeamSystem anagrafica names carry accented characters. Joinly transliterates the name and builds the login from your rules with a fallback pattern, so duplicate or accented names never produce a collision or a truncated, unreadable login.

• OU placement from the organigramma. Unità organizzativa, sede and centro di costo 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.

• Matricola as the matching key. Names change; the matricola does not. Joinly matches the AD object on the matricola, so a name change or rehire updates the existing user rather than creating a duplicate.

• Edition and module differences. TeamSystem HR, Studio HR and Dipendenti in Cloud expose slightly different object models. Joinly maps to the fields your edition actually returns, confirmed against your tenant during setup.

• 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 TeamSystem 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 distribution and wholesale company with around 1,300 staff across a head office and three regional depots, running TeamSystem HR but still living in an on-premise Active Directory for its warehouse and ERP systems. Every new warehouse operative, driver or office clerk starts as a TeamSystem ticket that IT processes by hand in AD — creating the object, choosing the depot OU, building the login, adding groups. With seasonal peaks and frequent moves between depots the queue never empties, and new joiners wait until day two or three for their account.

Connect TeamSystem to Active Directory with Joinly and that work disappears. The Joinly AD Agent creates each user in the right depot OU on the start date, builds a unique sAMAccountName transliterated from accented surnames, adds the correct security groups, moves people on a transfer and disables accounts on the termination date with a 30-day grace window — all driven by the change in the TeamSystem anagrafica and keyed on the matricola.

“Seasonal peaks used to bury us in AD tickets, and accented surnames broke half the logins we typed by hand. Now an account is simply ready in the right depot OU, transfers move themselves, and we can show the auditor exactly which TeamSystem change created every bit of access.” — Head of IT, distribution and wholesale company

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.