Connect & Integrate with Slack

Last updated: August 31, 2026

Introduction

This guide covers connecting Slack to YeshID as an application: keeping your Slack membership in sync, provisioning and deprovisioning accounts, and letting new hires add themselves to Slack during an onboarding.

Once connected, YeshID imports:

  • Users, the members of your Slack workspace

  • User groups and their memberships

  • Bots and apps, as non-human resources

A note on Slack plans: what YeshID can do with Slack depends on your Slack plan. Slack gates several of the capabilities this integration relies on — user groups, SCIM provisioning, and the org-wide admin APIs are all plan-dependent, and Slack changes these requirements from time to time. If an action isn't available to you, or a sync returns fewer users than you expect, check your Slack plan first.

Choosing how to sync users

There are three ways to connect Slack for user sync. Pick one.

Option

Use it when

What you get

Slack (prebuilt)

You have a single Slack workspace

Imports users, user groups, and bots. Adds and removes users from Slack user groups

Slack (Enterprise Grid) (prebuilt)

Your Slack org is on the Enterprise Grid plan

Everything above across every workspace in the org, plus creating and deactivating users, inviting, assigning and removing a user for a specific workspace, and workspace role management

SCIM

You need automated provisioning and you are on Slack Business+ without Enterprise Grid

Auto sync, auto provisioning, and auto deprovisioning through a Slack app you create yourself

💡 SCIM requires the Slack Business+ or Enterprise Grid plan.

Steps

1. Connect Slack for user sync

Follow whichever option you chose above.

Option A: The prebuilt integration

Before you start: ensure you have the necessary permissions to add applications in YeshID, and double-check that you are selecting the correct workspace to avoid syncing issues.

  1. Navigate to your Applications page.

  2. Click on Slack.

  3. Click Connect.

  4. Click Authenticate.

  5. Pick the correct Slack workspace. If you use this browser profile or account to log into multiple workspaces, the authentication flow may default to a different workspace.

  6. Click on your Slack workspace. Pick the workspace you want YeshID to manage.

  7. Click Allow.

  8. Enable the Import Users operation to sync users.

  9. Click Integration.

  10. The successful sync will now automatically import your users.

Option B: SCIM

This option uses a Slack app that you create and own.

  1. In Slack, create a new application.

  2. Enter your app details — app name and description.

  3. Add the relevant scopes. Navigate to OAuth Permissions and add users:read, users:write, and admin, then add the redirect URL https://app.yeshid.com/api/v1/applications/oauth/response.

  4. If you are using Enterprise Grid, you must also acknowledge that you have removed hardcoded information, and enable public distribution.

  5. In YeshID, connect the application. Set the integration type to SCIM and enter the Client ID and Client Secret from the app you just created.

  6. Authorize the connection. On Enterprise Grid, pick the Organization from the dropdown. On Business+, pick the workspace in the selector at the top right.

  7. Test the import. Enable Import Users, then click Test Request. If users populate, the connection has succeeded.

  8. Enable the remaining actions and save.

Note: once an integration is connected, your apps will usually sync once every 24 hours.

2. Add your Slack invite link

Adding your workspace's invite link lets new users add themselves to Slack during an onboarding.

  1. Navigate to your Slack workspace settings and copy the invite link.

  2. In YeshID, head to Applications > Slack.

  3. Click Edit, add the invite link, and hit Confirm.

Now when doing an onboarding with /Add User to Application for Slack, a user will receive an email from Slack to add themselves into your organization.

Known limitation with Google SSO: if a Slack workspace is set to use Google SSO, it is not possible to create an invite link. If you are using SCIM, use the provided user creation features instead.

FAQ

How does YeshID decide which Slack users to import?

There is no email-domain filter. YeshID imports every member Slack returns, then tries to match each one to a person in YeshID.

The only accounts YeshID deliberately skips are bots, apps, and Slackbot.

What does YeshID store for each Slack account?

Field

Where it comes from

External ID

The Slack member ID, which begins with U

Account name

The member's real name in Slack

Email

The email on the member's Slack profile

Status

Slack's deactivation flag. Deactivated Slack members are imported as deactivated accounts, not skipped

Role

Workspace Owner, Workspace Admin, or Regular Member

Login Type

Set to MFA when Slack reports two-factor enabled

Why do I see users who aren't on our email domain?

This is expected, and YeshID isn't adding anyone. Slack's member list reflects workspace membership, not your email domain, so everyone Slack considers a member is imported. In most workspaces that includes:

  • Guests — multi-channel and single-channel guests such as contractors, vendors, and agencies invited into specific channels. They are genuine workspace members with their own external email addresses.

  • Slack Connect collaborators — people from other organizations you share channels with.

  • Personal or legacy addresses — someone who joined with a personal address before your domain was enforced.

  • Deactivated members — Slack still returns them, so they import as deactivated accounts.

Current limitation: YeshID does not yet record Slack's guest and external flags, so a guest, a Slack Connect collaborator, and a full member all look the same on the Accounts tab. Slack's own admin console is the authoritative place to check account type today.

How can I tell whether one of those accounts is legitimate?

  1. In YeshID, go to Access > Applications > Slack and open the Accounts tab.

  2. Note the account's External ID, the Slack member ID beginning with U.

  3. In Slack, open your workspace admin's member management page and look up that ID or email. Slack shows the account type: full member, multi-channel guest, single-channel guest, or deactivated.

  4. Back in YeshID, resolve the account:

    • Someone you track — choose Map identity to link the account to their person record in YeshID.

    • Legitimate but external, such as a vendor or Slack Connect partner — open Map identity and clear the selection to save the account as human and unmapped. This records a deliberate decision, so later syncs won't re-match it.

    • Shouldn't be in Slack at all — remove them in Slack. They'll import as deactivated on the next sync.

How does YeshID match Slack accounts to people?

YeshID resolves each imported account in this order:

  1. A mapping you set by hand always wins, including a deliberate "leave unmapped."

  2. Otherwise, the account's email is matched against your people and their directory identities, including aliases if alias mapping is enabled for your organization.

  3. Otherwise, a uniquely matching full name.

Anything still unresolved shows as Unmapped in the Identity / Owner column. Unmapped accounts are the ones worth reviewing: they're access YeshID can see but can't yet attribute to a person.

What happens to bots and apps?

They aren't lost. Import Resources inventories them separately as Non-human bot resources, so you can still review them and assign owners.

Can YeshID create and deactivate Slack accounts?

It depends on how you connected:

  • Slack (prebuilt, single workspace) — no. Use the invite link during onboarding instead.

  • Slack (Enterprise Grid) — yes, including per-workspace invite, assign, and remove.

  • SCIM — yes, auto provisioning and auto deprovisioning.