Supplemental Slack info for you and your team.Tips and tools for beginners and experts alike.Get familiar with Slack Enterprise Grid for large organizations.If you're curious about what's new in Slack — and what's changed — you're in the right place.Develop your skills and prepare to become Slack Certified!Launching a new team or joining one for the first time?
Our easy-to-read guides help your team work better, together, from day one.Ready to level up? Browse our time-saving tricks and practical tips for
making Slack work for you.All kinds of teams thrive with Slack — take a look at our department-specific guides.
More coming soon!From channels to search – learn how Slack works from top to bottom.Want to learn more about setting up your team? Look no further!Welcome to Slack! Nice to see you here. Let’s get started!Adjust your profile and preferences to make Slack work just for you.Connect, simplify and automate. Discover the power of apps and tools.Tips and tools for beginners and experts alike.
Slack is experiencing some connectivity issues — please stand by. Check
If your preferred identity provider doesn’t have a connector with Slack, you can use a custom SAML connection.
Note: We’re happy to help troubleshoot your setup, but we can’t always guarantee your connection will work with Slack. Let us know if you have any problems and we’ll see what we can do.
Follow these parameters to configure your custom SAML connection.
Slack supports Identity Provider (IDP) Initiated Flow, Service Provider (SP) Initiated flow, Just In Time provisioning and automatic provisioning through our SCIM API.
For SP-initiated single sign-on, go to https://yourdomain.slack.com.
SSO post-backup URL
https://yourdomain.slack.com/sso/saml (Also known as the Assertion Consumer Service URL)
SAML logout endpoint
Bear in mind: Slack does not support single logout or session duration configured in your IdP.
Slack supports HTTP POST binding, not HTTP REDIRECT. You must configure HTTP POST bindings in the IdP metadata.
Your IdP must ensure a user is both authenticated and authorised before sending an assertion. If a user isn’t authorised, assertions should not be sent. We recommend your identity provider to redirect people to an HTTP 403 page or something similar.
Slack requires that the SAML response is signed, and you will need to paste a valid X.509 .pem Certificate to verify your identity. This is different from your SSL certificate.
End-to-end encryption key
If you require an end-to-end encryption key for your IDP, you can find a certificate by clicking the Advanced Options button located in your workspace's SSO settings. You can then tick the Sign AuthnRequest preference to reveal Slack's public encryption key.
Note: If you want to connect your Active Directory Federation Services (ADFS) instance, read ADFS single sign-on for details.
Who can use this feature?
Only Workspace Owners can access this feature.
Available to workspaces on the Plus subscription and Slack Enterprise Grid.
Thanks a lot for your feedback.
Thanks for your feedback.
If you’d like a member of our support team to respond to you, please send a message to firstname.lastname@example.org.
Whoops! We’re having some problems. Please try again later.