How does Joinly sync Fluida to Active Directory?

Joinly reads each change in Fluida in the cloud through the API, then hands the action to the Joinly AD Agent inside your network, which makes the change in Active Directory. The Fluida people directory holds who works where; the agent is the only component that touches your domain.

1. Joiner. HR adds the person in Fluida and assigns them to a Sede, Reparto and Team. Joinly reads the new record, determines the role from those fields, 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 Sede, Reparto or Team, 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 assignment is removed, so permissions stay aligned with where the person actually works.

3. Leaver. When the person is set to leave in Fluida — or their end date passes — Joinly instructs the agent to disable the AD account and optionally move it to a disabled-users OU, so no account is left active after someone has gone.

Example: A construction SME runs Fluida for attendance and shifts across several sites and an on-premise AD for its project and CAD systems. It hires a site foreman in Fluida, assigned to the Nord Sede and the Cantieri Reparto. On the next sync the AD Agent creates the user in the Nord > Cantieri OU, sets a unique sAMAccountName, and adds the Site-Operations group. When the foreman later moves to the office as a project planner, the agent moves the object to the office OU and swaps the groups the same day.

What manual AD account management costs

Without automation, every account starts as a message from HR that an admin works through in Active Directory Users and Computers by hand — creating the object, choosing the OU, building the sAMAccountName, adding groups. Fluida has no native AD writeback, so the alternative is Microsoft’s Entra provisioning agent fed by a custom SCIM client — limited mapping, no role-to-group logic, and development you have to own. Either way the decisions still fall to people.

• Onboarding delays. New joiners — often site or shift staff who need access from day one — wait for an AD account and group access while a request sits in a queue.

• Permissions that don’t keep up (privilege creep). When movers change Sede or Reparto, 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 — a real problem in high-turnover, project- and shift-based teams.

Joinly vs. the Entra provisioning agent for AD

Fluida has no native AD writeback. The native route is Microsoft’s Entra provisioning agent, fed by a custom SCIM client you build against API-driven inbound provisioning. Here’s how that compares to the Joinly AD Agent for a Fluida-driven AD setup.

Watch-outs when connecting Fluida to Active Directory

A few Fluida-specific details decide whether this connection stays reliable in a shift-based, SME setting.

• 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 — common in high-turnover teams — never produce a collision or a truncated, unreadable login.

• OU placement from Sedi and Reparti. A Sede or Reparto doesn’t map one-to-one to your OU structure. Joinly builds explicit rules that place each user — and move them on a transfer between sites — into the correct OU.

• Frontline staff without a work email. Many shift and site workers are identified by badge or personal contact in Fluida rather than a company mailbox. Joinly builds the sAMAccountName and UPN from name plus a Sede code with a fallback, so every account still gets a unique, predictable login.

• Read-only, scheduled sync. Fluida’s API is export- and integration-oriented, so Joinly connects with a Read Only API key and reads the directory on a frequent schedule. The agent applies the changes in AD; Joinly never writes back to Fluida.

• 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 Fluida 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 construction SME with around 180 employees across several sites, running Fluida for attendance and shifts but still living in an on-premise Active Directory for its project, estimating and CAD systems. Every new labourer, foreman or office hire starts as a message to IT that gets processed by hand in AD — creating the object, choosing the OU, building the login, adding groups. With crews moving between sites and seasonal work, the queue never empties, and new starters wait days for their account.

Connect Fluida to Active Directory with Joinly and that work disappears. The Joinly AD Agent creates each user in the right OU on the next sync, builds a unique sAMAccountName even for staff without a work email, adds the correct security groups, moves people when they change site and disables accounts when they leave, with a grace window — all driven by the record in the Fluida people directory.

“Crews move between sites constantly and we hire seasonally, so AD was always out of date. Now an account is simply ready in the right OU, a move to another site just changes the access, and we can show exactly which Fluida change created every login.” — Head of IT, construction SME

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