Voiceflow supports SAML 2.0 authentication through either an SP or IdP initiated flow. SP is Service Provider, i.e. Voiceflow, and IdP is Identity Provider, i.e. Okta or a custom SAML implementation.
SSO configuration page
<aside> 💡 Implementation Details
Voiceflow provides (after IdP is set/saved):
Voiceflow requires from IdP:
*On the IdP side, they will need to send the Email identifier (urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress
) to uniquely identify SSO users
</aside>
Ensure your workspace/organization are under an enterprise plan, and you are a workspace admin, you will be able to see the SSO/SAML configuration page.
Contact Voiceflow customer success to flag all relevant workspaces as part of an organization, and ensure anyone configuring SAML SSO settings is an admin of the workspace.
To access all the SP information, just press “Save Configuration” to generate a authentication provider profile.
Once everything is filled out and saved, an IdP-initiated login flow should be possible for the sysadmin to try.
<aside> ♻️ To retroactively add existing Voiceflow accounts to SAML, contact Voiceflow customer success.
</aside>
For an SP-initiated login flow, contact Voiceflow customer success to flag a specific email domain name. This is done for verification and security purposes.
Whenever a login is detected with the email domain, the user will be prompted to Log In via SSO.