Configure SSO with Okta

Learn how to enable logging into Turtl with Okta

Maruša Barle avatar
Written by Maruša Barle
Updated over a week ago

Before getting started:

To configure this integration you'll need to have an Okta account with admin privileges. If you don’t have admin privileges, please contact your account administrator.

Step 1 - Go to Applications

Click on the down arrow next to ‘Applications’ in the menu on the left-hand side and click ‘Applications’.

Step 2 - Create App Integration

Step 3 - Select SAML 2.0 option and hit 'Next'

Step 4 - Enter ‘Turtl’ in the ‘App name’ field and click ‘Next’

Step 5 - Configure SAML

Input the following values, replacing {yourTenant} with the name of your Turtl tenant:

Single sign on URL – https://{yourTenant}.turtl.co/user/login/callback

Audience URI (SP Entity ID) – https://{yourTenant}.turtl.co

Important: If you're using a custom domain (CNAME), please make sure you input the following instead:


Single sign on URL – https://{yourCname}/user/login/callback

Audience URI (SP Entity ID) – https://{yourCname}

Next, select the following from each dropdown menu:

Name ID format - ‘EmailAddress’.

Application username - ‘Email’.

Leave all the other fields blank and click ‘Next’.

Step 6 - Feedback

Select ‘I'm an Okta customer adding an internal app’ and clickFinish’.

Step 7 - Assign Turtl users

You should now be on the ‘Sign On’ tab of the new app.


Before you continue to the setup instructions, make sure you assign access to everyone who needs to use Turtl under the 'Assignments' tab.

Anyone who isn't on the list will not be able to use the Turtl app.

Step 8


Go back to the ‘Sign on’ tab and click on ‘View SAML Setup Instructions’ button.


You should see the following:

1. Identity Provider Single Sign-On URL

2. Identity Provider Issuer
3. X.509 Certificate

Please send ALL three items to support@turtl.co or your Customer Success Manager.

We will then finish the integration on our end and let you know once everything's complete.

Please note:

Only users who already have access to Turtl (i.e. are on the Turtl users list) will be able to log in to Turtl via Okta SSO and will have full access as defined by their role.

Anyone who isn't a Turtl user, but has been assigned access to Turtl via Okta, will be able to view Turtl Docs that are set to the ‘Anyone at my company’ access control.

Did this answer your question?