> ## Documentation Index
> Fetch the complete documentation index at: https://docs.marro.si/llms.txt
> Use this file to discover all available pages before exploring further.

# Company sign-in

> Let your team sign in with your company's identity provider, keep accounts in step with it, and set the rules for how everyone signs in.

An organization administrator manages this in **Settings → Team → Sign-in security**. If company sign-in isn't in your plan, the page shows which plan includes it. Every change asks you to confirm it is you (your password, a code from your authenticator app, or your company sign-in) and is recorded in the activity log. With the Activity log in your plan, **Sign-in activity** on the same page shows every sign-in, failure and change, with a CSV export.

## Connect your identity provider

Company sign-in works with any provider that supports OpenID Connect: Microsoft Entra ID, Google Workspace, Okta, OneLogin, JumpCloud, Keycloak and others.

1. Choose **Add connection** and your **Identity provider**. Marro shows the exact steps for it and the redirect address to copy into your provider.
2. Enter the **Issuer**, **Client ID** and **Client secret** from your provider. The secret is stored encrypted and never shown again. If the issuer is wrong, Marro says so under the field before saving anything.
3. Choose **Test connection** and sign in with your provider. Check the details it received, then **Turn on**. The test also says whether your provider reported two-step for that sign-in (see [Two-step sign-in after company sign-in](#two-step-sign-in-after-company-sign-in)).

Turning a connection off or deleting it, removing a domain, revoking a provisioning token and **Sign everyone out** each ask you to confirm first, because they stop people signing in.

Not the person who manages your provider? **Send link** gives an IT colleague a setup link that can add and test connections and domains, and nothing else. It lasts seven days and you can **Cancel link** at any time; an expired or cancelled link tells your colleague to ask you for a new one.

## Prove your email domain

**Add a domain** (such as *yourclinic.in*), add the DNS record Marro shows to your domain, then **Check record**. Only verified domains can be used for company sign-in, and public email domains (gmail.com and the like) cannot be claimed. For each domain, choose what happens to **New company sign-ins** from people not yet in Marro: they join, they ask to join (you **Let in** or **Decline** them), or they are not let in.

## Rules for your team

* **Who must sign in through your identity provider:** everyone, or **For chosen roles**.
* **What people who don't have to use company sign-in may use:** password with a code or passkey, and a code by WhatsApp or email in the app.
* **Break-glass owners:** at least one owner with a passkey who can always sign in, so a provider outage never locks you out.
* **Admins use a passkey or authenticator app** for two-step sign-in.
* How long a session lasts, and when an idle one ends.
* Allowed IP ranges (leave empty to allow sign-in from anywhere). **Add my address** adds the one you are using now.
* **Sign everyone out** ends every session on the web and in the app at once.

## Roles, teams and branches from your groups

Group rules give people a role, teams and a branch from the groups your provider sends (**Groups claim**). **Add rule** for each group, in **Priority** order; people with no matching rule get the default role.

## Keep accounts in step (SCIM)

In **Provisioning**, **Create token** gives your provider the SCIM address and a token. Your provider then adds, updates and deactivates people in Marro, and deactivating someone there signs them out of Marro everywhere. **Revoke** a token to stop it.

## On the web

On the sign-in screen, choose **Continue with company SSO** below the Google and Microsoft buttons, then enter your work email. Marro opens your company's sign-in page when it finds a match. If it can't find one, your email stays filled so you can correct it or go back and choose another sign-in option.

For a sign-in code, choose **Sign in with a mobile number** below the email form.

## In the app

On the sign-in screen, **Continue with company SSO** asks for your work email, opens your provider in the browser and brings you back signed in, the same way as on the web. If your provider already asked for a second factor, the app doesn't ask for Marro's code either. If your company asks an admin to let new people in, the app says your request was sent.

## Two-step sign-in after company sign-in

If your identity provider already asked for a second factor (an authenticator, a security key, a code by text or a fingerprint), Marro does not ask for its own authenticator code on top, on the web or in the app. Marro knows this from what your provider reports about the sign-in. Providers that don't report it, such as Google Workspace, sign in as before: after your company sign-in, Marro asks for your authenticator code if you have set one up.

Platform administrators always give Marro's own code.

## Confirm it's you with your company

Some changes, such as sign-in settings, ask you to confirm it is you first. If you sign in through your company, choose **Continue with** and your connection's name. Marro sends you to your provider to sign in again, then brings you back to the same page. You then have five minutes to make the change.

If you have no password, authenticator or passkey in Marro, this is the only way to confirm. Your provider must sign you in afresh: if it reuses an earlier sign-in, Marro asks you to try again. Only the company account linked to you can confirm.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.