.png)
.svg)
Connect Rippling and Slack to automate account provisioning, group membership, and SSO — so every new hire has access on day one and every departure is secured the moment offboarding begins.
Before enabling provisioning, we audit the client's existing Slack user base against their Rippling employee records. Mismatched emails, personal accounts used for work, and manually-created accounts that aren't tied to Rippling are all common — and each one will cause a conflict when provisioning goes live if not resolved first.
We then configure Rippling's SAML SSO for Slack, define provisioning rules using Supergroups tied to the correct employee attributes, and map department and role structures to the right Slack channel groups. For clients with existing Slack workspaces, we run a reconciliation pass to match existing accounts to Rippling records before flipping the provisioning switch.
We also configure Workflow Studio automations for common use cases — new hire welcome messages, manager notifications, and approval alerts — so the integration does more than just manage access from day one.
For US teams, confirm your Slack workspace is on a plan that supports SCIM provisioning (Pro or above) before enabling Rippling provisioning — Basic plan workspaces do not support automated user lifecycle management. For Enterprise Grid customers, Rippling manages users at the org level across all workspaces from a single place. Canadian and ROW teams operating as separate Slack workspaces within a Grid org should confirm entity-to-workspace mapping in Rippling before enabling provisioning to avoid cross-entity access errors.
Slack provisioning in Rippling is near-instant for most standard setups. When a new hire's start date is reached and their onboarding workflow triggers, their Slack account is typically created within minutes. Deprovisioning on termination is similarly fast — access is revoked as soon as the offboarding action fires in Rippling, with no manual IT step required.
Yes — Rippling supports Slack Enterprise Grid provisioning, including managing users and groups at the organization level. This allows you to provision users to both the main Grid organization and their primary workspace, and manage IDP groups, from a single place in Rippling. This capability was expanded in Rippling's February 2026 release.
Yes — Rippling's Workflow Studio lets you trigger custom Slack messages based on any HR event or field change in Rippling. Common uses include welcome messages to new hires, manager alerts when a direct report's role changes, automated check-ins tied to probation end dates, and approval notifications pushed directly into Slack. These are configured in Rippling's no-code workflow builder without any custom development.
Rippling assigns employees to Slack channels and groups dynamically based on their attributes in Rippling — department, role, location, management level, employment status, or any custom field. When an employee's attributes change (promotion, team transfer, location change), their Slack group memberships update automatically to match. No manual channel management required.
Yes — this is one of the most common IT configuration tasks we handle during Rippling implementations. Getting SSO, provisioning rules, and group membership logic right from the start prevents a range of downstream issues including orphaned accounts, incorrect channel access, and offboarding gaps. We also review existing Slack user data for mismatches with Rippling records before enabling provisioning to avoid conflicts on go-live.
