SSO FAQs

What SSO protocols are supported?

We exclusively support OpenID Connect (OIDC) for SSO integrations. Please note that SAML2 is not currently supported.

Does the platform offer native Multi-Factor Authentication (MFA)?

No, the platform does not have a built-in MFA system. To enforce MFA for external users, they must be managed via your EntraID (Azure AD) directory and access the platform through SSO. This allows you to leverage your own corporate security policies.

Can SSO be made mandatory for all users?

Yes. Administrators have the option to enforce SSO for all accounts within a specific domain. This ensures that users cannot bypass corporate security protocols by using standard login credentials.

How are user accounts linked between the platform and EntraID?

The system maps accounts using the following priority:

  1. Email Address: The system first attempts to match the primary email field.

  2. UPN (User Principal Name): If no match is found via email, the system will check the UPN field.

Can users log in using their Microsoft account without a custom SSO setup?

Yes. Since EntraID accounts are inherently Microsoft accounts, users can utilize the "Login with Microsoft" option.

Note: Depending on your organization's security settings, this may require a one-time approval from your EntraID administrator.

What happens when I switch from a standard account to an SSO account?

If you are transitioning from a traditional password-based account to an SSO-enabled account, a security verification step is required:

  • Sign in using your SSO credentials.

  • Check your inbox for a verification email.

  • Approve the request via the link provided to finalize the link between your existing profile and your SSO identity.