Single Sign On (SSO)

In addition to the user authentication provided by Wordbee Translator, you can also use single sign-on (SSO), which authenticates your users with your existing enterprise sign-on pages. Management of user credentials then happens outside of Wordbee. User name, role and other fields can automatically updated from your systems whenever a user authenticates.

This is for customers requiring tight integration with existing authentication mechanisms. A centralised management of hundreds to thousands of users across all corporate applications adds substantial efficiences and is often a regulatory requirement. We are proud to be part of your success.

Compatibility

We support the SAML-2 industry standard. This makes it very likely that your existing user management smoothly integrates with Wordbee Translator:

• Microsoft Active Directory Federation Services (ADFS)

• Microsoft Entra ID (formerly known as Azure Active Directory)

• AWS Directory Service + AWS Single Sign-On

• Okta

• Ping Identity

• Salesforce

• OneLogin

• Many more commercial and open source solutions

Features

• Redirects users to your login page.

• Users are authenticated by your systems. Credentials never reach our servers.

• Users are managed in your systems, from email, name, company etc. Remove a user and he/she can no longer login into Wordbee.

• Users can be created in Wordbee Translator immediately upon first sign on (if enabled).

• Full support of "SAML claims" and field mapping options: User and company fields in Wordbee can all be updated from your systems.

• Choose which companies SSO updates: list the companies to update, or the companies to leave unchanged. Users from other companies still sign in normally, but their profile and company details are not overwritten from your systems.

• Possibility to propose single sign on for some users and classic Wordbee Translator sign on for others.

• Any strong authentication such as 2-factor logins can be implemented via your SSO system.

Choosing which companies SSO updates

By default, SSO refreshes user and company fields from your systems every time a user signs in. You can limit this with one of two lists:

• Companies to update: only users from the listed companies have their details refreshed. Use it when only a few companies should be updated, for example your client companies, while suppliers and freelancers sign in through the same SSO.

• Companies to leave unchanged: users from the listed companies keep their details. Use it when a few companies are managed another way, for example through a nightly data sync via the Wordbee Translator API.

You can use one list or the other, not both.

For a company whose details are not updated:

• Users still authenticate and sign in normally.

• New users are still created on first sign-on.

• No attributes are overwritten: neither the user's fields (name, email, role) nor the company record (address, contact details).

• If SSO-only login is enforced, that enforcement still applies.

If SSO assigns a user to a different company, the user is moved in every case, and their record in the new company is filled in from your systems.

Getting started