Note: This feature is available on our Grow AI and Scale AI plans. Please contact support if you want to upgrade your plan.
Your company may be using a Single Sign-On (SSO) provider, which lets employees log in to many different platforms using the same credentials. Turtl supports any SSO provider based on the SAML 2.0 protocol, such as Okta, Microsoft Entra ID (formerly Azure AD), or Google. This article explains the main benefits of integrating your SSO provider with Turtl, so you can decide whether it's right for your team.
Streamlined access for Turtl users
Just as your team probably uses a variety of services every day, entering separate credentials for each one quickly becomes a chore. With SSO integration, Turtl users don't need to remember a separate Turtl password — they sign in once through your SSO provider and can then access Turtl freely alongside their other tools.
Note: For this to work, users need to be provisioned both within your SSO provider and in the Turtl app.
SSO provider:
Turtl:
Protect your internal content
Some companies use Turtl Docs for internal communication and want to keep them protected from external readers. Turtl can restrict access to a Doc so that only logged-in users or users with SSO access can read it — and this works for both drafts and published Docs.
With SSO integration, every employee provisioned within your SSO provider can read your internal Docs without you having to add them to Turtl as viewers or create new credentials for them.
Note: In this case, readers only need to be provisioned within your SSO provider — they don't need a Turtl account.
To protect a Doc this way, apply the "Anyone at my company" access control policy. You can find the steps in Applying Single Sign-On (SSO) settings to users and Turtl Docs.
Better control over user management
With SSO integration, provisioning and deprovisioning of employees all happens in one place — your SSO provider. This is especially useful for large companies, because access can be managed by your SSO provider administrators rather than by people with Turtl admin licenses.
This applies to SSO-protected Docs, and to Turtl user logins on the condition that SSO sign-in is required for your account.
Known reader data
SSO integration also gives you known reader data. Because readers sign in through your SSO provider, you can see exactly who has (or hasn't) read your Docs — which is especially useful for internal communications.
How to get started
Turtl supports any SSO provider based on the SAML 2.0 protocol, including Okta, Microsoft Entra ID (formerly Azure AD), Google, and others. Please reach out to Customer Support or your Customer Success Manager, specify which SSO provider you are using, and they will provide personalized instructions for your account.
If your SSO provider is based on a different protocol, we'll need to have a conversation with you to understand your requirements, so we can provide a brief and quote for any development required. Please contact your Customer Success Manager or Customer Support for further details.