How does Joinly sync BambooHR to Active Directory?

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

1. Joiner. HR adds the new hire in BambooHR. Joinly reads the record, determines the role from department, location and job title, 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 hireDate.

2. Mover. When someone changes department, location or job title, 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 terminationDate, Joinly instructs the agent to disable the AD account and optionally move it to a disabled-users OU. An employment-status change to a non-active status is treated the same way, so access is removed when the person actually stops working — not only on a formal termination.

Example: A creative agency runs BambooHR and an on-premise AD across two studios. It hires a motion designer with a hire date next Monday. Joinly reads the record, and on Monday morning the AD Agent creates the user in the Studio-A > Creative OU, sets the sAMAccountName to a unique pattern, and adds the Creative-Team group. When the designer later moves to the production 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 BambooHR notification that an admin works through in Active Directory Users and Computers by hand — creating the object, choosing the OU, building the sAMAccountName, adding groups. BambooHR has no native way to write to on-premise AD, so without a tool the decisions all fall to people, and small teams without an IAM function feel that most.

• Onboarding delays. New joiners wait for an AD account and group access while a request sits in someone's inbox, losing productive days in their first week.

• Permissions that don't keep up (privilege creep). When movers change department or location, 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 — easy to miss when there's no automated trigger from BambooHR.

Joinly vs. building it yourself for AD

BambooHR can't write to on-premise AD on its own, and the native Entra provisioning agent only relays cloud-provisioned data. Here's how Joinly compares for a BambooHR-driven AD setup.

Watch-outs when connecting BambooHR to Active Directory

A few details decide whether this connection stays reliable as you grow.

• 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.

• OU placement from a flat HR model. BambooHR only has department, division and location — there is nothing that maps to an OU. Joinly builds explicit rules that place each user, and move them on a transfer, into the correct OU from those flat fields.

• Reliance on custom fields. Data that decides OU or group often lives in BambooHR custom fields, exposed only by numeric field ID. Joinly discovers them via /meta/fields and maps the ones you need, so a local site code or contract type can drive AD placement.

• Employment-status changes. A move to on-leave or contractor-to-FTE is a status change, not a hire or termination. Joinly reads employmentHistoryStatus and disables or re-enables the AD object accordingly, so access matches the person's real status.

• 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 BambooHR 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 creative agency with around 180 employees across two studios, running BambooHR but still living in an on-premise Active Directory for its design workstations and file shares. Every new designer, editor or account manager starts as a BambooHR notification that one overloaded admin processes by hand in AD — creating the object, choosing the OU, building the login, adding groups. With freelance contracts and frequent moves between teams the work never empties, and new joiners wait until day two or three for their account.

Connect BambooHR to Active Directory with Joinly and that work disappears. The Joinly AD Agent creates each user in the right OU on the hire date, builds a unique sAMAccountName, 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 HR change in BambooHR.

"An account is simply ready in the right OU when the designer walks in, moves between teams sort themselves out, and we can show exactly which BambooHR change created every bit of access."

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