Docs
Security: MFA & SSO
Protect console access with TOTP multi-factor authentication and SAML single sign-on.
Multi-factor authentication (TOTP)
Each member enables MFA from their own profile (Account → Security → Two-factor authentication). Org admins can see whether a member has MFA enabled in the team list.
- Enroll — click Set up authenticator, scan the QR code with any TOTP app (Google Authenticator, Authy, 1Password…), and save the recovery codes.
- Activate — enter a one-time code from the app to confirm enrollment.
- Sign-in — after the Google sign-in step, the console challenges for the current TOTP code.
- Remove — go to the same screen and click Remove (requires a current TOTP code to confirm).
Save the recovery codes somewhere safe — they bypass TOTP and are the only way back if you lose your device.
SAML single sign-on
SAML SSO is configured at the org level by an ADMIN or OWNER. Your identity provider can only sign in people whose email is on a domain your organization has verified — a signature from your IdP alone is never enough, so no organization's IdP can vouch for anyone else's users.
- Go to SSO / SAML → Email domains in the console and add your domain (for example
acme.com). Shared mailbox providers such as gmail.com can't be added. - Publish the TXT record it shows — name
_croombit.acme.com, valuecroombit-verify=…— at your DNS provider, then press Verify. A domain can be verified by only one organization. - In Identity provider, paste your IdP's metadata XML or metadata URL.
- Register Croombit as a Service Provider in your IdP using the details below.
- Choose the role given to people added automatically on their first SSO sign-in (Viewer by default; never Owner).
- Save and test with a non-owner account before enforcing SSO.
| SP endpoint | Value |
|---|---|
| Metadata | GET /auth/saml/:orgId/metadata |
| Login init (redirect users here) | GET /auth/saml/:orgId/init |
| ACS (Assertion Consumer Service) | POST /auth/saml/:orgId/acs |
Anyone your IdP signs in on a verified domain is added to your organization on their first SSO sign-in, with the role you chose — no invite needed. Someone on a domain you haven't verified is refused, and the login page tells them why. Their session only gains access to your organization. Enforce SSO applies to people on your verified domains; members on other domains (contractors, guests) keep signing in with Google or an email link. Removing your last verified domain turns SSO off.