How does Joinly sync Silae to Active Directory?

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

1. Joiner. The payroll team enters the new salarie in Silae. Joinly reads the fiche salarie and its emploi, determines the role from etablissement, job title and department, 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 on the record.

2. Mover. When someone changes job, department or etablissement in Silae, a new emploi record is generated. Joinly reads it and 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. Silae does not push a leaver event, so Joinly derives the exit (date de sortie) from the employment record and instructs the agent to disable the AD account on that date and optionally move it to a disabled-users OU — so no closed contract is left with a live account.

Example: A construction company runs Silae and an on-premise AD across three regional depots. It hires a site foreman with a start date next Monday, attached to its Nantes etablissement. Joinly reads the new emploi, and on Monday morning the AD Agent creates the user in the Nantes > Site-Ops OU, sets the sAMAccountName to a unique pattern, and adds the Site-Operations group. When the foreman later moves to the head-office estimating team, 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 message from the payroll team that an admin works through in Active Directory Users and Computers by hand — creating the object, choosing the OU, building the sAMAccountName, adding groups. Silae exposes a REST API, but it has no role-to-group logic and no leaver event, so the decisions — and the timing — 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 job or etablissement, old security-group membership often stays attached, so people accumulate rights they no longer need.

• Forgotten offboarding. Because Silae never sends a leaver event, an exit can slip past IT entirely — the AD account stays enabled, which is a security and audit risk.

Joinly vs. a custom Silae-to-AD integration

Silae has no native path to on-premise Active Directory, so the alternative is scripting against the Silae Paie REST API and writing to AD yourself. That is a lot of build and a lot of maintenance. Here’s how the two compare for a Silae-driven AD setup.

Watch-outs when connecting Silae 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. The Silae matricule is not stable enough to use as the login, so Joinly keys the object on a durable identity instead.

• OU placement from etablissement. Etablissement, societe and job 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.

• No native leaver event. Silae is payroll-first and does not emit an offboarding trigger. Joinly derives the exit (date de sortie) from the employment record and has the agent disable the account on that date, so leavers are handled reliably even though the source never announces them.

• Partner-administered, per-dossier API access. API access on the Silae dossier is opened by your expert-comptable or Silae partner and scoped per dossier with a subscription key. Joinly reads only the dossiers you authorise, so the AD sync respects that partner-driven access model.

• 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 Silae 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 regional construction group with around 1,800 employees across four depots and a head office, running Silae for payroll but still living in an on-premise Active Directory for its project and site systems. Every new labourer, foreman or estimator starts as a message from the payroll team that IT processes by hand in AD — creating the object, choosing the depot OU, building the login, adding groups. With seasonal site crews and frequent moves between depots the queue never empties, and new starters wait until day two or three for their account. Worse, when a contract ends payroll simply closes the emploi and IT is never told, so old accounts sit enabled for weeks.

Connect Silae 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 derived exit date with a 30-day grace window — all driven by the HR change in the Silae dossier.

“Site crews change constantly and payroll closes contracts without telling us. Now an account is ready in the right depot OU on day one, transfers move themselves, and closed contracts disable on the exit date — and the auditor can see which Silae change caused every change.” — Head of IT, construction group

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