Workplace and industry applications

Connecting Slack, Atlassian and Bitwarden to HR or Entra ID

An integration with Slack, Atlassian Cloud or Bitwarden creates users from Microsoft Entra ID or the HR system, puts them in the right groups and disables them on departure. KoppelHet builds this from Entra ID, AFAS or Workday, with nested groups in Bitwarden, returning colleagues and guests with an end date in Slack, and groups directly from HR when only HR knows the right department and job.

Last updated: 9 November 2026

Discuss your integration All about Accounts in applications

What it is

Collaboration tools and password vaults run on groups. Whoever is in a team's group sees that team's channels, spaces and shared collections. If the group is wrong, the access is wrong.

Things go wrong at the edges: a group of subgroups that stays empty, a former colleague who cannot get a new account, or an email address that changes after a marriage and produces a second invitation.

How the integration handles it

If a group in Entra ID consists of subgroups, KoppelHet reads the nested groups and puts the members in the Bitwarden group itself.
Bitwarden recommends matching on the objectId from Entra ID instead of the email address. KoppelHet sets it once for existing members and reports who cannot be matched.
Directly from AFAS an employee goes into the Bitwarden group of their unit and of the location above it, plus extra groups per job from a table HR maintains.
Slack cannot delete a user, only deactivate them. When a former colleague returns, KoppelHet reactivates the old Slack user, with their earlier messages and channels.
Externals become a guest in Slack with the end date of their assignment as expiry date.
Groups from AFAS get a fixed prefix and the unit code in Atlassian, so a department named like a default group does not silently drop out and small renames do not need a new group.

Edge cases we handle

Atlassian only allows automatic account creation from an external source with Atlassian Guard Standard. We check that before the start.
A full update in Atlassian clears every field that is not sent. KoppelHet only changes the fields that come from HR, so a self-chosen time zone or language stays.
A Slack username is at most 21 characters and shares the namespace with channel names. On a clash KoppelHet chooses an agreed variant.
Disabling in Entra ID revokes the member in Bitwarden. Only after permanent deletion, after thirty days, does the member leave the organisation, so a mistake can be undone without a new invitation.

What KoppelHet does

KoppelHet builds the integration from Entra ID or directly from AFAS or Workday, depending on where the right department and job are kept. Nested groups, guests, rehires and matching existing members are part of the design.

Common integrations

Microsoft Entra ID → Bitwarden

Entra ID to Bitwarden integration: members and groups from Entra ID, access closed on disable

AFAS Profit → Bitwarden

AFAS to Bitwarden integration: members and groups from AFAS, revoked after the last working day

Okta → Bitwarden

Okta to Bitwarden integration: members and groups from Okta, revoked on deactivation

Microsoft Entra ID → Slack

Entra ID to Slack integration: Slack accounts and user groups from Microsoft Entra ID, on rehire too

Workday → Slack

Workday to Slack integration: Slack account on the first working day, manager and team from Workday

AFAS Profit → Atlassian Cloud (Jira en Confluence)

AFAS to Atlassian integration: employees from AFAS Profit as managed accounts in Jira and Confluence

Frequently asked questions

Does the integration work with Slack Enterprise?

Yes. KoppelHet also connects a Slack Enterprise organisation, with former colleagues who return, guests with an end date and the start date in the profile.

What happens to a leaver's messages and pages?

Slack and Atlassian deactivate the account. Messages, Confluence pages and Jira issues stay and remain linked to the leaver.

What happens when a former colleague returns?

Slack cannot delete a user, only deactivate them. KoppelHet reactivates the old Slack user, with their earlier messages and channels, instead of creating a second account.