Single Sign on (SSO) - Overview

SigNoz Cloud - This page applies to SigNoz Cloud editions.
Self-Host - This page applies to self-hosted SigNoz editions.

SigNoz supports single sign-on (SSO), allowing users to authenticate through an external identity provider (IdP) instead of maintaining SigNoz-specific passwords.

What’s supported

  • SAML 2.0: Available on SigNoz Cloud and Enterprise Self-Hosted
  • OIDC: Available on SigNoz Cloud and Enterprise Self-Hosted
  • Google Workspace (OAuth2): Available on Community Edition, SigNoz Cloud and Enterprise Self-Hosted

How SSO works in SigNoz

At a high level, you connect your organization’s email domain to an IdP, and SigNoz defers authentication to that IdP.

  1. Authenticated Domain: You register a domain like example.com under Settings → Organization Settings → Authenticated Domains.
  2. Choose Method: For that domain, select SAML, OIDC, or Google (for Workspace) and provide the IdP details.
  3. Just‑in‑Time access: Users with emails on that domain can sign in via your IdP without a prior invite.
  4. Attribute/Claim Mapping: Map IdP attributes (SAML) or token claims (OIDC/Google) to SigNoz user fields like email, display name, groups, and role.
  5. Role Mapping: Automatically assign SigNoz roles (VIEWER, EDITOR, ADMIN) based on IdP group memberships or a direct role attribute — no manual role assignment needed.

User deprovisioning

SigNoz does not automatically remove user records when a user is deactivated or removed from your IdP. Once removed from the IdP, the user can no longer sign in via SSO, but their SigNoz account remains until an administrator deletes it manually from Settings → Organization Settings → Members or via the API.

Setup at a glance

  • Go to Settings → Organization Settings → Authenticated Domains
  • Add your organization’s email domain (e.g., example.com)
  • Click Configure SSO and choose a method
  • Save and test from an incognito window
  • Optionally toggle Enforce SSO for that domain
  • If you encounter any issues, you can temporarily use password authentication by appending ?password=Y to the login URL, e.g. <your-instance-url>/login?password=Y.

IdP‑Initiated SSO setup

If your provider supports IdP-initiated logins, you will see an option to set the Relay State URL in the IdP's configuration UI.

  • Copy the IdP Initiated SSO URL from the Authenticated Domains section and set this as the Relay State URL in your IdP

Next steps

Looking for step-by-step setup? See the user guides below:

Is this page helpful

Last updatedJune 12, 2026

Edit on GitHub