How does Joinly sync Partena Professional to Active Directory?

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

1. Joiner. The employee is set up in Partena and declared through Dimona. Joinly reads the new employment record, determines the role from department, function and cost centre, 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 contractual start date.

2. Mover. When someone changes function, department or cost centre in Partena, 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. When the departure is recorded in Partena — the contract end and Dimona out — Joinly instructs the agent to disable the AD account on the end date and optionally move it to a disabled-users OU.

Example: A facility-services company runs its payroll through Partena and an on-premise AD across three regional depots. It hires a cleaning-team lead with a start date next Monday. Joinly reads the new employment record, and on Monday morning the AD Agent creates the user in the Region-North > Operations OU, sets a unique sAMAccountName from the bilingual name, and adds the Field-Staff group. When the team lead later moves to a supervisory role, 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 the Partena payroll consultant that an admin works through in Active Directory Users and Computers by hand — creating the object, choosing the OU, building the sAMAccountName, adding groups. Partena’s partner integrations import HR data into other tools, but nothing writes to your domain, so every AD decision still falls 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, 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 — especially with short and seasonal contracts, where the contract end can pass unnoticed in AD.

Joinly vs. a manual export to Active Directory

Partena’s partner connectors move HR data between HR tools, and a hand-built CSV/SFTP export gets data out — but neither writes users into your domain. Here’s how the Joinly AD Agent compares with the do-it-yourself alternatives for a Partena-driven AD setup.

Watch-outs when connecting Partena Professional to Active Directory

A few Partena-specific 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 — and bilingual, accented Belgian names make collisions likely. Joinly transliterates and builds the name from your rules with a fallback pattern, so duplicate names never produce a collision or a truncated, unreadable login.

• OU placement from payroll structure. Partena’s department, function and cost centre 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.

• The data channel depends on your Partena setup. As a social secretariat, Partena surfaces data through ProSalary or ExpertSalary and its partner API, or through a secured export — the channel and cadence vary by contract. Joinly reads whichever channel your setup exposes and drives the agent from it.

• Contract end vs. actual last day. The Dimona out and contract end date drive offboarding. Joinly keys the agent’s disable action to the recorded end date, with an optional grace window, so the account is retired on the right day — important with the short and seasonal contracts common in Belgian workforces.

• 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 Partena Professional 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 facility-services company with around 1,800 employees across cleaning, catering and security contracts, running its payroll through Partena but still living in an on-premise Active Directory for its site and scheduling systems. Every new team member starts as an email from the Partena payroll consultant that IT processes by hand in AD — creating the object, choosing the OU, building a login from a Dutch or French name, adding groups. With high turnover and seasonal contracts the queue never empties, and new joiners wait until day two or three for their account.

Connect Partena Professional 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 from the bilingual name, adds the correct security groups, moves people on a transfer and disables accounts on the contract end date with a 30-day grace window — all driven by the change in the Partena payroll administration.

“With our turnover, onboarding by hand from payroll emails was a full-time job on its own. Now an account is simply ready in the right OU on the start date, leavers switch off on the contract end date, and we can show the auditor exactly which Partena change created every bit of access.” — Head of IT, facility-services company

The outcome this setup is designed for: onboarding drops from days to zero touch, leavers no longer slip through on short contracts, and the team can walk into its next NIS2 assessment with a complete, source-backed audit trail.