Skip to main content
Edition: Enterprise Single sign-on is an Enterprise module. RAGSuite supports two OIDC identity providers so your organization can sign in with the accounts it already uses:
  • Google
  • Microsoft Entra ID
Organization admins configure each provider on its own tab (Google / Microsoft Entra) in the Single Sign-On settings screen. You can enable one or both; the same email can be linked to both providers. Community password auth and 2FA remain available without SSO — see Authentication.
1

Confirm Enterprise entitlement

SSO requires an active Enterprise license. Complete Activation first.
2

Register RAGSuite with your identity provider

Google: in Google Cloud Console, create an OAuth client and add the Google Console redirect URI shown in RAGSuite.Microsoft Entra ID: in the Microsoft Entra admin center, create an app registration, add the Redirect URI shown in RAGSuite, and create a client secret.Keep client secrets out of shared documents and chat.
3

Configure SSO in RAGSuite

On the provider’s tab, enter:
4

Test the connection

Use Test connection before enabling. It checks that the identity provider is reachable and that the client ID and secret are accepted.
5

Verify sign-in

Only invited team members whose email matches an allowed domain can sign in — accounts are not created automatically. Sign in with Google or Microsoft and confirm the user lands in the expected org and project access. Keep password auth available as a break-glass path until SSO is proven.
Env flags such as SSO_ENABLED exist in CE templates for wiring; product SSO requires Enterprise entitlement and configuration. RAGSuite SSO uses OIDC with Google or Microsoft Entra ID.

Interactive tour