How does Joinly sync Securex to Active Directory?

Joinly reads each HR change from your Securex HR platform (Exact Officient) in the cloud through the Officient REST API, then hands the action to the Joinly AD Agent inside your network, which makes the change in Active Directory. Officient holds the authoritative people, team and contract record; the agent is the only component that touches your domain.

1. Joiner. HR completes the hire in the Securex/Officient platform. Joinly reads the new person, team and function, determines the role, 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 contract start date.

2. Mover. When someone changes function, team or department in Officient, 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 role is removed, so permissions stay aligned with the actual job.

3. Leaver. On the contract end date, Joinly instructs the agent to disable the AD account and optionally move it to a disabled-users OU. A grace window keeps the account recoverable for a set period before it is retired.

Example: A Belgian hospitality group runs its HR in the Securex/Officient platform and an on-premise AD across several hotels. It hires a front-office employee for its Brussels site with a start date next Monday. Joinly reads the new person and contract, and on Monday morning the AD Agent creates the user in the Brussels > FrontOffice OU, sets a unique sAMAccountName from the French record with a diacritic-safe rule, and adds the FrontOffice group. When the employee later moves to the reservations 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 an email 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. Securex’s HR platform holds the people and contract data, but there is no first-party connector that writes it to your on-premise AD, 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 team, 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 an expired fixed-term contract can leave an active account behind for weeks if nobody acts on it.

Joinly vs. the Entra provisioning agent for AD

Securex has no native path to on-premise AD, so the realistic alternatives are Microsoft’s Entra provisioning agent fed from a cloud source, or scripting the Officient API to AD yourself. Here’s how the Joinly AD Agent compares for a Securex/Officient-driven AD setup.

Watch-outs when connecting Securex 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. French and Dutch names with accents make this harder. Joinly builds it from your rules with a diacritic-safe transform and a fallback pattern, so duplicate or accented names never produce a collision or a truncated, unreadable login.

• OU placement from teams and functions. Officient models a person through their team and function rather than a deep legal-entity hierarchy, so these 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.

• Read HR, not the payroll batch. Securex runs a live HR platform (Officient) alongside the payroll files that go to your sociaal-secretariaat klantenadviseur. Joinly reads the Officient REST API, so AD is driven by up-to-date HR data rather than a periodic payroll export.

• Employee number availability. The linked payroll employee number is only exposed on certain Securex/Officient integrations. Joinly derives a stable identifier from the fields your tenant actually returns, so matching to the right AD object never depends on a value that may be missing.

• 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 Securex 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 Belgian hospitality group with around 900 employees across several hotels and restaurants, running its HR in the Securex/Officient platform but still living in an on-premise Active Directory for its front-office and property-management systems. Every new receptionist, kitchen or housekeeping hire starts as an email from HR that IT processes by hand in AD — creating the object, choosing the site OU, building the login, adding groups. With seasonal contracts and staff moving between properties, the queue never empties, and new joiners wait until day two or three for their account.

Connect Securex to Active Directory with Joinly and that work disappears. The Joinly AD Agent creates each user in the right site OU on the contract start date, builds a unique sAMAccountName from the French or Dutch record, adds the correct security groups, moves people on a transfer between properties and disables accounts on the contract end date with a 30-day grace window — all driven by the HR change in the Officient platform.

“Seasonal turnover used to bury us in AD tickets. Now an account is simply ready in the right site’s OU when the person starts, a move between hotels updates access by itself, and we can show the auditor exactly which Securex change created every bit of access.” — Head of IT, hospitality group

The outcome this setup is designed for: onboarding drops from days to zero touch, seasonal leavers stop lingering in AD, and the team can walk into its next NIS2 assessment with a complete, source-backed audit trail.