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 OWNER. Once active, members whose email domain matches are redirected to your identity provider instead of the Google sign-in screen.
- Go to Team → Security → Single sign-on → Configure SAML.
- Paste your IdP's metadata XML or metadata URL.
- Register Tripticonsent as a Service Provider in your IdP using the details below.
- Save and test with a non-owner account before enforcing SSO for all members.
| 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 |
SSO does not replace invites — a member must be invited before SSO lets them into the console. Uninvited users who authenticate via your IdP see an "access denied" screen.