Single sign-on

Monita sign-in lives at accounts.monita.ai and supports, out of the box:

• Email — sign in with your work email address.
• Google — one-click sign-in with a Google Workspace or Gmail account.
• Microsoft — one-click sign-in with a Microsoft / Entra ID account.

All three connect to the same Monita account when they share an email address, so team members can use whichever they prefer. No configuration is needed — these work for every organization from day one.

Enterprise SSO (SAML / OIDC)

For organizations that require sign-in through their own identity provider — Okta, Microsoft Entra ID, Google Workspace SSO, or any SAML 2.0 / OIDC provider — Monita supports enterprise SSO enabled per company domain.

Once enabled, anyone signing in with an email on your domain is routed to your identity provider, and access is governed by your IdP’s own policies (MFA, device rules, offboarding).

To set it up, email support@getmonita.io from your work address with:

1. The email domain(s) to cover (e.g. yourcompany.com).
2. Your identity provider (Okta, Entra ID, etc.).

We’ll send the connection details for your IdP admin and verify the setup together. Enterprise SSO is available on enterprise plans — your account manager can confirm what’s included in yours.

Note

Enabling SSO doesn’t change anything inside Monita — roles and project access are still managed on Settings → Team; SSO only controls how people prove who they are.

FAQ

Do existing accounts survive the switch to enterprise SSO?

Yes. Accounts are keyed by email address, so a member who previously signed in with Google keeps their role, project grants and history — only the sign-in step changes.

Does SSO handle offboarding?

Disabling a user in your identity provider blocks new Monita sign-ins for them. Also remove them on Settings → Team to revoke access immediately rather than waiting for their session to expire.