Single Sign-On (SSO) lets your team access Ribeye through your existing identity provider, and multi-factor authentication (MFA) adds a second verification step. This article explains what each does, why to enable them, and how an admin sets them up.
The feature: SSO connects Ribeye to your organization's identity provider; MFA requires a second verification factor at login. The advantage: Your team uses
existing credentials and security policy instead of separate Ribeye passwords, and access follows your identity system. The benefit: Admins centralize access control and reduce password-related risk and support load.
What are SSO and MFA?
Single Sign-On (SSO) lets users log in to Ribeye with your organization's identity provider, so there's one set of credentials governed by your policy. Multi-factor authentication (MFA) adds a second factor — a code or device confirmation — on top of the password, so a stolen password alone can't grant access.
How it works
SSO is configured between Ribeye and your identity provider so logins route through it. MFA is enforced at sign-in. Once both are set, users authenticate through your system and access follows the roles you assigned.
How to set it up — For admins
1. Confirm your identity provider with your Customer Success (CS) Manager to scope the SSO connection.
2. Configure the SSO connection between Ribeye and your identity provider.
3. Enforce MFA for the account so every login requires a second factor.
4. Test with a single user before rolling out to the team.
5. Communicate the new login flow to users.
Best for
• Partner admins standing up secure access during onboarding.
• Organizations with an existing identity provider and security policy.
• Teams that need centralized access control.
Common questions
What is SSO? Single Sign-On — logging in through your organization's identity provider.
What is MFA? Multi-factor authentication — a second verification step at login. Why enable them? Centralized access control and reduced password risk.
Do I need an identity provider for SSO? Yes — SSO connects to your existing provider; confirm it with CS.
Can I enforce MFA without SSO? MFA adds a second factor at login; coordinate the setup with CS.
Who configures it? The admin, with CS support for the provider connection. Related articles
• First Login — Setting Up Your Account and User Permissions
• Inviting Users and Assigning Role-Based Access
• White-Label Setup — Branding, Logo, and Custom Domain
• Ribeye Product UI — A Map of the Platform
• Onboarding Checklist — What CS Needs From You in Week 1
Last updated: June 2026 · Questions? Contact your Customer Success Manager.