Google Workspace & Other Identity Providers - SAML Setup Guide
Last updated Nov 5th, 2026
Overview
SAML single sign-on (SSO) lets your team sign in to Common Room through your company's identity provider (IdP), so IT can manage access to Common Room alongside your other apps. Common Room works with any identity provider that supports SAML 2.0, including Google Workspace, JumpCloud, Rippling, and PingFederate.
Using Okta or Microsoft Entra ID? See the Okta - SAML Setup Guide or the Microsoft Entra ID - SAML Setup Guide.
Availability
SAML SSO is included on Essential, Advanced, and Enterprise plans. On older plans, it's included on Team and Enterprise but not on Starter. If you're not sure which plan you're on, contact your account team. Google and GitHub sign-in work on every plan with no setup.
How setup works
Your IdP admin sets up Common Room in your identity provider, and Common Room Support finishes the connection on our side:
- Email support@commonroom.io with your identity provider and your company's email domain. We'll reply with your connection name (for example, Google-Acme).
- Your IdP admin creates a SAML app for Common Room using the settings below.
- Send Support your IdP metadata URL. If your identity provider only offers a metadata file, as Google Workspace does, send the XML file instead.
- We create the connection and let you know when it's ready. To test it, go to app.commonroom.io, choose SSO, and enter your work email. You should be redirected to your identity provider's sign-in page.
SAML app settings
Enter these values when you create the SAML app in your identity provider, replacing {connectionName} with the connection name Support gave you:
| Setting | Value |
|---|---|
ACS URL (Reply URL) | https://login.commonroom.io/login/callback?connection={connectionName} |
Entity ID (Identifier) | urn:auth0:cr-prod:{connectionName} |
Required attribute
Common Room identifies users by email address. Add an attribute named email that contains the user's primary email address. Google Workspace, JumpCloud, Rippling, and PingFederate don't send it by default.
Google Workspace
- In the Google Admin console, add a custom SAML app for Common Room.
- Download the IdP metadata file from the app setup screen. You'll send this to Support.
- Enter the ACS URL and Entity ID from the table above.
- Under Attribute mapping, map the Google Directory attribute Primary email to the app attribute email. Without this, sign-in to Common Room (including the MCP server) can fail.
- Turn the app on for the users who need access, and send the metadata file to Support.
Other SAML 2.0 identity providers
For JumpCloud, Rippling, PingFederate, and other SAML 2.0 identity providers, create a SAML application using the settings above, add the email attribute, and send Support your metadata URL (or the metadata XML file if your identity provider doesn't offer a URL).
Require SSO (optional)
Once SSO is working, you can ask Support to require SSO for everyone on your email domain. This blocks other sign-in methods, such as Google sign-in. You can also give us specific admin email addresses that can still sign in another way, as a fallback in case your identity provider is unavailable or misconfigured.
If you require SSO, add new users through SCIM provisioning rather than inviting them from Common Room. Setup guides are available for Okta and Microsoft Entra ID; for other identity providers, contact Support.
FAQ
Our signing certificate is changing. What do we need to do?
Send Support your updated metadata URL (or metadata file) before the current certificate expires, and we'll update your connection.
We're moving to a different identity provider. How do we move our SSO setup?
Contact Support before you switch. We'll set up a new connection for your new identity provider.
