Skip to main content
INS // Insights

Joiner Access Reconciliation

Updated October 2026 · 7 min read

A joiner access reconciliation compares the access a new person was supposed to receive with the access that is actually on the account after they start. The joiner workflow grants birthright from a rule. People also copy a teammate's groups, approve a ticket outside the rule, or create the account before the HR record exists. Reconciliation is the diff that shows which of those happened. It is not the workflow itself. A workflow can report success and still leave an extra production group, or report nothing because nobody ran it.

Rutagon builds the diff beside the GRC platform the team already runs. That platform can store the new-hire ticket. It does not compare a versioned rule table to the directory the next morning. Security automation is the compare. Joiner, mover, and leaver automation is the grant and removal path. SOC 2 CC6.1 provisioning evidence is the authorization record. Reconciliation is how you show the authorization and the directory match, for starters, while the memory of "we set them up like the rest of the team" is still fresh.

What joiner access reconciliation compares

Three inputs, pinned to the start. The HRIS event: person, department, worker class, manager, and the start the HRIS recorded. The rule table version that was in force at that start: department and worker class map to groups, permission sets, and application roles. The directory after start: group membership, permission set assignments, and application roles on every identity we can tie to that person. Approved requests that add access beyond birthright are a fourth input. They are named grants, not a vibe. A ticket that says "same as a teammate" is not an approved request in this diff. It is unstructured, and every group that came from it shows up as extra until someone names it or removes it.

The rule version is pinned. Reconciling yesterday's starter against today's rule rewrites history. If the rule changed the same day, the row records which version ran. A later rule change can be a mover event. It is not a silent edit of the joiner result.

We run the compare twice. Once soon after the start, which mostly measures queue lag, and once after the provisioning SLA the company actually set. The first pass catches an account that never appeared. The second pass is the one we export. A single compare at the minute the HRIS event fires will mark every new hire as missing birthright, because the job has not finished. That report trains people to ignore it.

person: hris-902
worker_class: employee
department: support
rule_version: pinned at start
birthright_expected:
  - grp-support-standard
actual_groups:
  - grp-support-standard
  - grp-prod-admin
approved_requests: []
diff: extra grp-prod-admin
identities:
  - idp-17

Diff classes are small and closed. Missing birthright: the rule names a group and the identity is not in it. Extra grant: the identity is in a group that neither the rule nor an approved request names. No account: the HRIS says the person started, and no identity is linked. Account without a joiner: an identity exists and no HRIS start links to it. That is an orphan, not a joiner pass. Early access: in-scope grants exist before the start, outside whatever window the policy allows. Duplicate identities: two directory users for one HRIS person. We reconcile both. Birthright on one and extra admin on the other is not a clean starter.

Microsoft's provisioning docs, in user provisioning, describe how an identity provider pushes users into applications. That push is one way birthright arrives. It is not proof the push matched your rule. A successful provisioning log means the connector did what it was configured to do. Reconciliation checks the configuration against the rule you think you adopted. Those diverge when someone adds a group to the connector and not to the rule table, or the reverse.

Extras, copies, and the second identity

The extra production group is the finding that matters. It arrives because an administrator copied a senior teammate, because a ticket system's "clone user" button was the fastest path, or because a rehire kept old groups and also received new birthright. The row does not call that malicious. It calls it extra. The decision is remove, or convert into a named request with an owner and an end. A keep that says "they needed it on day one" without a named grant stays open. Day one is when extras hide. Access deprovisioning for joiner, mover, and leaver removes access later. It cannot remove an extra the joiner diff never recorded, if the later process treats every current group as authorized.

Duplicates are reconciled as one person. We do not mark the HRIS-linked identity clean and ignore the second login. The second login's groups are part of the actuals. If the second login has no owner, it is an orphan attached to a known person, which is worse than a stranger orphan because it looks explained. The export lists both identifiers.

No account is not fixed by reconciliation. The diff stays open. We do not create the user inside the evidence job. Creation is the provisioning workflow. The evidence job reports that the workflow did not produce an identity by the second pass. Closing the row because IT intends to create the account tomorrow deletes the miss. Tomorrow's pass can close it when the identity exists and the groups match.

Early access is a policy field. Some companies allow a short window before the recorded start. The window is on the policy version, in the same way the rule version is pinned. Grants inside the window are noted. Grants outside it are a diff. We do not hard-code a number of days into the job and call it the policy. Screening status is a different join. Whether the background check finished before access is not a column we silently add here. Mixing the two makes both samples harder to explain. The access diff answers "did they get the right grants." The screening diff answers "was the check done first."

Orphans are not force-matched on a display name. Two people can share a name. A match requires an identifier both systems store, or an explicit link a person confirmed. A fuzzy match can be a suggestion. It cannot be a pass. An unmatched identity with privileged groups is the top of the orphan list, reviewed on the same cycle as the joiner extras, not in a quarterly cleanup that never quite happens.

What we keep for the sample

The export for starters in the period is the rule version, the policy window, the expected grants, the actual grants, the approved request ids, the diff, and the decision with a read-back. A remove reads back as the group gone. A named request reads back as a request id that existed before the second pass, not a ticket written after the auditor asked. Rewriting a "same as a teammate" copy into a formal request after the fact is visible if the request time is after the diff time. We store both times.

Managers still have a role. They confirm the function and the department that selected the rule. They do not get to wave off an extra production group because the new person is covering a gap. The scope owner of that group decides. One-click acceptance from the manager is the same failure mode as any other privileged keep.

Rutagon's deliverable is the pinned rule, the two-pass compare, the diff classes, and the read-back. The provisioning workflow can stay whatever you have. Reconciliation tells you where it disagreed with the directory. That disagreement is the work. A dashboard that only counts "joiners processed" will stay green while the extra group sits there.

See what an Access & Credential Governance Diagnostic finds on starters whose grants do not match the rule. Contact Rutagon at rutagon.com/contact, 907-841-8407, or contact@rutagon.com.

Frequently Asked Questions

Is reconciliation the same as the joiner workflow?

No. The workflow grants and removes. Reconciliation compares the rule that should have applied with the directory after the start. A workflow can finish successfully and still leave an extra group, or never run and leave no account. The diff is the check. It does not replace the workflow, and it does not create users by itself.

What is an extra grant?

A group, permission set, or application role on the new identity that the pinned rule does not name and that no approved request names. Cloning a teammate produces extras. "Same as a teammate" is not a request id. The extra stays open until it is removed or converted into a named grant with an owner. The read-back is the directory, not the ticket status.

Why pin the rule version?

Because the rule changes. Comparing a starter to today's rule makes yesterday's correct birthright look like a miss, or hides an extra that today's wider rule now includes. The row stores the version in force at the start. A later rule change is a mover event, not a rewrite of the joiner result.

How do duplicate accounts get handled?

Both directory identities link to the one HRIS person, and both sets of grants are actuals. A clean birthright on the primary login does not excuse admin groups on the second login. Unmatched identities are not joined by display name. A privileged orphan stays on the list until an explicit link exists or the grants are gone.