# SAML single sign-on

Reps sign in to Chambr with the account they already use: Okta, Microsoft
Entra ID, Google Workspace, or any SAML 2.0 identity provider.

| | |
|---|---|
| Status | **Assisted** |
| Direction | Identity provider → Chambr (sign-in) |
| Set up by | Your identity provider admin, with Chambr |
| Time | About 30 minutes, plus a test sign-in |
| Data freshness | Email at each sign-in; name set when the account is first created |

## What you need

- An admin of your identity provider who can create a SAML app.
- The email domain your reps sign in with, for example `yourcompany.com`.
- Your Chambr contact, who turns SSO on for your account.

## What gets sent

| SAML attribute | Chambr | Required |
|---|---|---|
| NameID, or `email` | The user's email | Yes |
| `firstName` | First name | Recommended |
| `lastName` | Last name | Recommended |

Use exactly `firstName` and `lastName` (not `first_name`). Microsoft's
standard claim URIs for given name, surname and email address also work.
Chambr sets the name only when it creates the account at first sign-in; it
doesn't update it afterwards. Rename people under **Members** in Chambr.

## Set it up

### 1. Ask Chambr for the service provider details

Email your Chambr contact, or `support@chambr.ai`, with your email domain.
You'll get Chambr's service provider metadata: the ACS (reply) URL and the
entity ID.

### 2. Create the SAML app in your identity provider

- **Okta:** **Applications > Create App Integration > SAML 2.0**.
- **Microsoft Entra ID:** **Enterprise applications > New application >
  Create your own application**, then **Single sign-on > SAML**.
- **Google Workspace:** **Admin console > Apps > Web and mobile apps > Add
  app > Add custom SAML app**.

Enter Chambr's ACS URL and entity ID, set NameID to the user's email, and add
the `firstName` and `lastName` attributes.

### 3. Assign people

Assign the users or groups who should have Chambr to the app.

### 4. Send Chambr your identity provider's metadata

Send your Chambr contact the app's metadata URL, or its SSO URL and signing
certificate. Chambr turns SSO on for your domain, either **optional** or
**enforced**:

- **Enforced:** entering an email on your domain on Chambr's sign-in page goes
  straight to your identity provider.
- **Optional:** people can still sign in with a Chambr password; SSO users
  start from the Chambr tile in your identity provider's app launcher.

## Verify it works

1. Sign out of Chambr and start from the Chambr tile in your identity
   provider's app launcher. You land in Chambr signed in.
2. If SSO is **enforced**: sign out, open the Chambr sign-in page and enter an
   email on your domain. You're sent to your identity provider, and back into
   Chambr signed in.

## Limitations

- One identity provider per email domain.
- Sign-in creates the Chambr account on first use and takes a seat. Teams are
  set in Chambr.
- Removing someone in your identity provider stops them signing in; remove
  them under **Members** in Chambr too. Automatic removal (SCIM) is planned.

## Troubleshooting

| Symptom | Cause | Fix |
|---|---|---|
| "SSO sign-in failed" | The app's ACS URL or entity ID doesn't match Chambr's | Copy them again from Chambr's metadata |
| Users arrive named "SSO" | `firstName` wasn't sent when their account was created | Add the `firstName` and `lastName` attributes for new users, and rename existing ones under **Members** |
| "Your organization has reached its seat limit" | No free seat for a new user | Free a seat, or ask about more |
| A removed user can't come back from the app tile | Removed users must be re-invited first | Re-invite them in Chambr |

## Disconnect

Ask your Chambr contact to turn SSO off, then delete the SAML app in your
identity provider. Users keep their Chambr accounts. Accounts created through
SSO have no Chambr password: those users select **Forgot Password** on the
Chambr sign-in page to set one.
