Corporate SSO

Last updated: August 24, 2026Author: Jakub Pomykała

SimpleLocalize supports custom identity providers (SSO) for Business plan customers. With custom identity providers, you can manage your team members using your corporate identity provider (like Okta, OneLogin, Azure AD, Google Workspace, etc.). Users can log in to SimpleLocalize using their corporate credentials by providing an assigned identity provider (IdP) identifier in the URL at the SSO login page.

https://simplelocalize.io/login-sso/?idp=IDENTIFIER

Configuration

If you are a business customer, and you want to use single-sign-on (SSO) to manage your team members, please fill the SSO configuration form.

In case of any questions, please contact us at contact@simplelocalize.io.

OpenID Connect

Please provide us with the following information:

  • client_id
  • client_secret
  • authorized_scopes
  • attribute_request_method (GET or POST)
  • issuer_url
  • preferred corporate identifier or domain name

SAML2 protocol

Please provide us IdP metadata XML file or metadata document endpoint URL and preferred corporate identifier or domain name.

User mapping fields

We expect the following fields for user mapping:

  • email (required) - unique work email address
  • name (required) - first name, nickname, or display name
  • username (required) - unique identifier for the user pool at organization
  • profile_image (optional) - URL to image that will be displayed in the SimpleLocalize web app

Users on the first login will be automatically assigned as Team Administrators to the subscription and Project Administrators to every project in the subscription. After that, you can change their roles and manage their access level in the project settings.

Enforce SSO

If you want to make sure that team administrators who signed up through your identity provider always authenticate through your corporate SSO, you can turn on the Enforce SSO option. Go to the Team section, click Details next to the "Single Sign-On (SSO) is enabled for your organization" message, and enable Enforce SSO in the configuration modal. Only the subscription owner can change this setting.

When enabled, members who signed up through your identity provider (i.e. their account provider is your corporate SSO) will no longer be able to:

  • log in with a password,
  • log in with another authentication provider (e.g. Google, GitHub).