Skip to main content
SSO lets your team sign in to Flowla using their existing Okta credentials — no separate passwords, no extra accounts to manage.

​
Prerequisites

  • Admin access to your Okta account
  • Admin access to your Flowla workspace

​
Step 1 — Create an App Integration in Okta

Sign in to your Okta Admin Console, then navigate to Applications → Applications and click Create App Integration.
Okta Applications page with Create App Integration button highlighted

​
Step 2 — Select sign-in method and app type

Choose OIDC - OpenID Connect as the sign-in method and Web Application as the application type, then click Next.
New App Integration dialog with OIDC - OpenID Connect and Web Application selected

​
Step 3 — Configure the app integration

Fill in the following fields on the configuration page:
FieldValue
App integration nameAny name you wish (e.g. Flowla)
Client credentialsEnabled
Sign-in redirect URIhttps://app.flowla.com/sso
Sign-out redirect URIhttps://app.flowla.com/signin
AccessAllow everyone in your organization to access (recommended)
Immediate accessEnable immediate access (recommended)
App integration name and client credentials settings
Sign-in and sign-out redirect URI settings
Access settings with Allow everyone and Enable immediate access options
Enabling Allow everyone in your organization to access ensures all users can log in via SSO without needing individual app assignments in Okta.
Click Save to create the integration.

​
Step 4 — Copy your Client ID and Client Secret

After saving, open the General tab of your newly created app integration. Copy both the Client ID and Client Secret — you’ll need these when configuring Flowla.
General tab showing Client ID and Client Secret fields
The Client Secret is only shown once — copy it before navigating away. If you lose it, you’ll need to generate a new one from the General tab.
Protect your Client Secret by keeping it confidential. Avoid sharing it in public repositories, forums, or unencrypted channels.

​
Step 5 — Find your Identity Provider URL

Your Identity Provider URL is the base URL of your Okta account — the part of the address bar that appears before /admin.
Browser address bar showing the Okta URL with the base domain highlighted before /admin
For example, if your Okta Admin Console URL is: 
https://yourcompany.okta.com/admin/dashboard
Your Identity Provider URL is: 
https://yourcompany.okta.com

​
Step 6 — Enable SSO in Flowla

In Flowla, go to Settings → Security & Permissions and click Enable SSO. Fill in the form with the values you copied from Okta:
Flowla SSO setup form with Identity Provider URL, Client ID, Client Secret, and Email Domain fields
1

Enter your Identity Provider URL

Paste the base URL of your Okta account (e.g. https://yourcompany.okta.com)
2

Enter your Client ID

Paste the Client ID from the Okta app’s General tab
3

Enter your Client Secret

Paste the Client Secret from the Okta app’s General tab
4

Set your email domain

Enter the email domain your organization uses (e.g. yourcompany.com). Users with this domain will be required to sign in via SSO.
5

Save and test

Click Save to activate SSO. Open a new browser session and verify you can sign in via Okta.
Once set up, users with your organization’s email domain will be automatically redirected to Okta when signing in to Flowla.

​
Troubleshooting

Likely cause: The email domain entered in Flowla does not exactly match the domain of your users’ email addresses.Fix: Check the domain setting in Flowla for typos or extra spaces, ensuring it exactly matches your users’ email domain (e.g. yourcompany.com).
Likely cause: The Sign-in redirect URI in the Okta app is incorrect or has a trailing slash.Fix: Verify the Sign-in redirect URI in your Okta app is set to exactly https://app.flowla.com/sso with no trailing slash.
Likely cause: The Client Secret was not copied at creation time and is no longer visible in Okta.Fix: Generate a new Client Secret from the General tab of your Okta app integration, then update it in Flowla.
Likely cause: Individual users or groups are not assigned to the Okta app integration.Fix: Check the Assignments tab of your Okta app. If access is not set to Everyone, explicitly assign the required users or groups.