How to Sync Users Between Google Workspace and Slack (2026)
SyncMyGroup team · November 11, 2026
If your company runs on Google Workspace, Google already knows who works there and which team they are on. Slack should follow: new hires get an account, leavers lose access, and @platform contains the people in the platform Google Group. "Sync users between Google and Slack" covers three different jobs, and Slack handles each one differently depending on your plan:
- Signing in: people use their Google account to get into Slack.
- Accounts: Slack accounts are created when someone joins Google Workspace and deactivated when they leave.
- Groups: Slack user groups and channels match the Google Groups people are in.
This guide goes through each, what you need for it, and where the gaps are.
Job 1: sign in to Slack with Google
The simplest piece. Members can sign in to Slack with their Google account, and an admin can let anyone with a company email address (for example @yourcompany.com) join the workspace without an invitation.
That gets people in. It does nothing when they leave: removing someone from Google Workspace does not deactivate their Slack account. Without the next step, an admin has to deactivate leavers in Slack by hand, and that is exactly the step that gets missed during offboarding.
Job 2: create and deactivate Slack accounts from Google Workspace
This is user provisioning. Google Workspace can act as the identity provider for Slack: you add Slack as a SAML app in the Google Admin console and turn on automatic provisioning, so Google creates, updates and deactivates Slack accounts as people join, change and leave.
The catch is the Slack plan. Automatic provisioning into Slack runs on Slack's SCIM API, and SCIM is only available on Business+ and Enterprise plans. On Pro, there is no provisioning path: you get sign-in with Google, and deactivation stays manual.
| What you want | Free | Pro | Business+ | Enterprise |
|---|---|---|---|---|
| Sign in with Google | Yes | Yes | Yes | Yes |
| Auto-join by company email domain | Yes | Yes | Yes | Yes |
| Accounts created and deactivated from Google (SCIM) | No | No | Yes | Yes |
| Slack user groups | No | Yes | Yes | Yes |
| User groups managed by SCIM | No | No | Workspace level | Org level |
If you are on Business+ or Enterprise, set provisioning up: it is the single biggest offboarding improvement for a Google Workspace company. Google's admin help center has the current step-by-step for the Slack app.
Job 3: keep Slack user groups in sync with Google Groups
This is the one most teams actually mean, and the one neither sign-in nor account provisioning solves. Your teams are already defined as Google Groups: platform@, design@, sales-emea@. You want @platform in Slack to contain exactly the people in platform@, and to change when the Google Group does.
Your options:
- By hand. Someone edits the Slack user group whenever the Google Group changes. This is why most user groups are out of date.
- SCIM group push. On Business+ and Enterprise, an identity provider can push groups into Slack. Two limits to know: SCIM can't set a user group's
@handle, so someone still has to set it in Slack, and what gets pushed depends on your identity provider's connector. Details in Slack SCIM provisioning alternatives. - A group sync tool. It reads the Google Group and updates the Slack user group (and, if you want, channel membership) through Slack's regular API. This works on Pro as well as Business+ and Enterprise, because it doesn't use SCIM.
SyncMyGroup is a group sync tool. Pick a Google Group as the source and a Slack user group or channel as the destination, preview the changes, and turn it on. When someone joins or leaves the Google Group, the Slack group follows. It also syncs from Microsoft Azure (Entra ID), Jira, Linear, GitHub, GitLab, Zoom, PagerDuty and Opsgenie. It is free for up to 5 users, then $1 per user per month (50% off the $2 list price). Full setup: how to sync Google Groups to Slack user groups.
A setup that covers all three jobs
For a Google Workspace company on a paid Slack plan:
- Turn on sign-in with Google and auto-join for your company domain, so new hires get into Slack on day one.
- On Business+ or Enterprise, turn on provisioning from Google Workspace, so leavers are deactivated automatically. On Pro, add "deactivate in Slack" to your offboarding checklist.
- Sync team groups from Google Groups into Slack user groups, so handles and channels follow the team structure you already maintain in Google.
With all three, a change in Google Workspace flows through to Slack without anyone editing Slack directly. Offboarding becomes one action instead of a checklist. More on that in offboarding: removing users from groups.
FAQ
Does Slack sync with Google Workspace automatically?
Partly. Sign-in with Google works on every plan. Creating and deactivating Slack accounts from Google Workspace needs Slack's SCIM provisioning, which is only on Business+ and Enterprise. Keeping Slack user groups in line with Google Groups needs either SCIM group push or a group sync tool.
Can I sync Google Groups to Slack on the Pro plan?
Not with SCIM, which Pro doesn't include. A group sync tool that uses Slack's regular API works on Pro, because user groups themselves are available on Pro.
Does removing someone from Google Workspace remove them from Slack?
Only if provisioning is set up (Business+ or Enterprise). Otherwise their Slack account stays active until an admin deactivates it.
Will a synced Slack user group keep its @handle?
Yes, with a group sync tool: the handle is set once in Slack and the tool only changes membership. With SCIM, the handle can't be set through provisioning and has to be set in Slack.
Start with one Google Group on the free tier, or see the Google Group → Slack workflow.