---
title: "Set up SSO and SCIM provisioning"
url: "/help/buuk/sso"
updated: "2026-11-19T08:13:37.939Z"
---
# Set up SSO and SCIM provisioning

Open **Settings → SSO & SCIM**. Workspace owners configure single sign-on; editors and viewers see the settings read-only. SSO is an Enterprise feature, and the page gates accordingly.

## OpenID Connect

The OIDC panel is the fastest path for providers such as Keycloak, Auth0, or Google Workspace. Fill in the **Company email domain** that should join automatically, the provider’s **Issuer URL**, your **Client ID** and **Client secret**, the **Scopes** to request (the default is `openid, email, profile`), and an **Auto-join role** of Viewer or Editor that new sign-ins receive.

Press **Look up endpoints** and Buuk reads the provider’s discovery document to fill in the authorization and token endpoints. If discovery fails, expand **Advanced: manual endpoints** and paste them yourself; the userinfo endpoint is optional.

## SAML 2.0

The SAML panel is for Okta, Entra ID, or any SAML 2.0 identity provider. Enter the **Company email domain**, the **IdP entity ID (issuer)**, and the **Single Sign-On URL**, then paste the provider’s X.509 certificate including the `BEGIN` and `END CERTIFICATE` lines. Choose the same auto-join role as any OIDC connection.

Give your provider Buuk’s service provider metadata URL, `/api/auth/saml/metadata?domain=your-domain.com`, when configuring the SAML app. The page shows the exact URL with copy buttons.

## Prove you own the domain

Saving either connection activates a DNS TXT check. Buuk shows the record under the email-domain field: a name like `_buuk-sso-verify.acme.com` with your workspace ID as the value. Add it in your DNS provider, then save again. This stops another company from claiming your domain’s logins — and public email providers such as Gmail or Outlook are rejected outright.

## What teammates see

Once a connection is active, anyone signing in at your email domain goes through your identity provider and joins the workspace with the auto-join role. Disconnecting stops new SSO sign-ins immediately; members who are already in stay signed in.

## SCIM provisioning

On the same page, the **SCIM provisioning** panel issues bearer tokens so Okta, Entra ID, or Rippling can create, update, and remove members at `/api/scim/v2`. Press **Generate token** and copy it now — the plaintext is shown once and only its hash is stored. The list shows each token’s prefix, when it was last used, and a Revoke action; revoking stops any sync using it immediately.

## Keep a recovery owner

Keep at least one owner who signs in with email and password rather than the provider. If your identity provider has an outage, that owner can still reach Settings, disconnect SSO, and restore password sign-ins for everyone.

## Worked example

Acme runs Okta. An owner opens **Settings → SSO & SCIM**, creates a SAML app in Okta, copies the entity ID, sign-on URL, and certificate into Buuk, adds the `_buuk-sso-verify` TXT record, and saves. Okta gets the metadata URL. Every `@acme.com` sign-in lands in Buuk as an editor, and a SCIM group sync frees seats the same week people leave.

## Troubleshooting

**The save keeps failing on the TXT record**

DNS changes can take a short time to propagate. Paste the exact name and value shown on this page, wait a few minutes, and save again. The dashboard copies the exact record for you.

**Endpoint discovery failed**

Check the issuer URL for typos, then expand Advanced and paste the authorization and token endpoints from your provider’s documentation manually.

**The SAML certificate is rejected**

Paste the PEM exactly, including the `-----BEGIN CERTIFICATE-----` and `-----END CERTIFICATE-----` lines. Some providers export several certificates; use the signing one.

**The domain is already taken**

Buuk allows one workspace per email domain. Remove SSO from the other workspace first, or use a different domain and invite those teammates instead.

## Related

- Roles and seat rules: [Members, roles, and groups](./members-roles-and-groups).
- What SSO costs and where it applies: [Plans and billing](./plans-and-billing).
- Protect your owner account itself: [Account security](./account-security).
- Machine access without the browser: [API tokens and MCP](./api-tokens-and-mcp).