All plans have access to SSO via sign-in with Slack. If you have your Slack sign-in configured using SAML, then we’ll use that.
How to enable SAML
Prerequisites
To setup SAML, you’ll need to be an Admin or Owner inside incident.io to initiate the integration, and you’ll need to have someone with Admin access to your IdP to complete the setup in your provider. Note : If you’re just setting up incident.io for the first time, you need to first sign in using Slack, and then enable SAML.Admins can do it, if they have the Manage security settings permission for the Admin role.
Setup
- Open the incident.io dashboard and go to Settings > Security .
- Click
Connectto begin the setup flow. - Choose your identity provider from the list of options and then follow its associated set up instructions.
- Test your connection using the button provided.
- You should now be connected

Configuring domains
Once connected to SAML, you can configure which user email domains should be associated with your organisation. By default, only the user performing the setup’s domain is set. Click on theConfigure domains button to add any other domains for your organisation.
Note : If you have a sandbox environment on incident.io, we recommend not using SAML with it. This is so that anyone logging in with SAML can be automatically redirected to your production instance based on their domain.

Logging in with SAML
Once you’ve set up SAML, all users in your organisation will have to sign in using SAML. If a user tries to sign in using Slack, they’ll be redirected to your IdP to confirm their access to incident.io. To sign in, click on theLogin with SAML SSO button, then enter your email address. Upon clicking Login button, you’ll be redirected to your IdP to authenticate, before being directed back to incident.io.
