# Enterprise sign-in: what is and isn't available

> Single sign-on with Microsoft Entra ID, Google Workspace, any OpenID Connect or SAML 2.0 provider, and SCIM provisioning are available on every plan. MFA in Orbit itself is not yet.

Source: https://docs.bifrostorbit.com/orbit/admins/enterprise-sign-in/

Many IT teams ask for the same list. Here is where Bifröst Orbit stands on each item today. Everything here is included on every plan.

| You may ask for | Today |
| --- | --- |
| Single sign-on with Microsoft Entra ID | Yes, through your own Entra app. See [Connect Microsoft SSO](https://docs.bifrostorbit.com/orbit/admins/connect-microsoft-sso/). |
| Single sign-on with Google Workspace | Yes, for your Workspace domains. See [Connect Google SSO](https://docs.bifrostorbit.com/orbit/admins/connect-google-sso/). |
| Okta, Auth0, OneLogin, JumpCloud, Keycloak or any other OpenID Connect provider | Yes. See [Connect an OpenID Connect provider](https://docs.bifrostorbit.com/orbit/admins/connect-oidc-sso/). |
| SAML 2.0 | Yes, with any SAML 2.0 identity provider. See [Connect a SAML provider](https://docs.bifrostorbit.com/orbit/admins/connect-saml-sso/). |
| Require SSO for your email domain | Yes. See [Choose how your people sign in](https://docs.bifrostorbit.com/orbit/admins/set-up-sign-in/). |
| Roles and satellites from your identity provider | Yes, from Microsoft app roles or groups, or from groups sent by your OpenID Connect or SAML provider. |
| SCIM provisioning | Yes, SCIM 2.0, tested with Okta and Microsoft Entra ID. See [Set up SCIM provisioning](https://docs.bifrostorbit.com/orbit/admins/set-up-scim/). |
| Multi-factor authentication in Orbit itself | Not yet. With SSO, your identity provider's policies apply, including MFA. |
| An audit log of members, roles and sign-in settings | Yes, in Orbit, with each satellite keeping its own for what happens inside it. See [The audit trail](https://docs.bifrostorbit.com/orbit/admins/audit-trail/). |

## What you can use today

**Microsoft Entra ID:** Orbit signs people in through an app registration in your own tenant, so your conditional access and MFA rules apply. App roles or groups can map to an Orbit role and to the satellites a person gets. People in your Microsoft directory can also be picked when you add members. See [Set up the Entra app](https://docs.bifrostorbit.com/orbit/admins/set-up-entra-app/).

**Google Workspace:** people sign in with their work account on the domains you add. Personal Google accounts, such as Gmail, are refused.

**OpenID Connect and SAML:** connect as many providers as you need, each with its own button on your sign-in page and its own email domains. Orbit only accepts addresses on those domains through each connection, and never lets a connection take over an account that belongs to another organisation. Groups your provider sends can map to roles and satellites.

**Role mapping:** if someone matches several rules, they get the highest role and every satellite those rules give. Taking someone out of a group in your provider takes the access away at their next sign-in.

**SCIM provisioning:** your identity provider adds people before they first sign in, changes their access when their groups change, and removes leavers at once in every satellite. Owners and people you added by hand are never changed.

**Required SSO:** once a domain such as `northwilds.com` requires a sign-in, nobody on it can sign in with an email code or another connection instead.

**Sessions:** a signed-in session in the browser lasts at most eight hours, then people sign in again.

## What isn't there yet

**Multi-factor authentication in Orbit itself:** Orbit relies on your identity provider for MFA. There is no separate MFA step in Orbit.

**Sign-in started from your provider's dashboard (IdP-initiated SAML):** sign-in always starts in Orbit, because a sign-in your provider starts on its own cannot be tied to a request. Point the dashboard tile to your Orbit sign-in address instead.

**Single sign-out:** signing out of your identity provider does not sign people out of Orbit. Their session ends after at most eight hours, and removing them with SCIM ends their access at once.

**One audit log for everything:** Orbit's audit trail records changes to members, roles, sign-in settings and provisioning, but what happens inside a satellite stays in that satellite's own record: the audit log in CMS Orbit, and the audit trail in Booking Orbit, Commerce Orbit, Travel Orbit, Careers Orbit, Insights Orbit and Presence Orbit. There is no single view across them yet.

If one of these decides whether you can use Bifröst Orbit, tell us at [support@bifrostorbit.com](mailto:support@bifrostorbit.com). It helps us decide what comes next.
