> ## 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.

# Two-step sign-in

> Use an authenticator, passkeys and backup codes to protect your Marro account.

Open **Sign-in security** in your account menu, or go to `/account/security`. These settings protect your personal Marro login across all your organizations. They are available after the sign-in security migration is installed.

## Set up an authenticator

1. Verify your password or an existing sign-in method. Verification lasts five minutes.
2. Choose **Set up authenticator**. Scan the QR code in your authenticator app, or enter the text secret manually.
3. Enter the six-digit code to finish. Two-step sign-in is enabled only after this code is checked.
4. Generate backup codes and save them somewhere separate from your sign-in device.

If you signed up with Google or Microsoft and have no password or existing factor, use **Forgot password** to set a password by email before enrolling. If you sign in through your company, choose **Continue with** and your company's connection to verify instead (see [Company sign-in](https://docs.marro.si/guides/company-sign-in.md#confirm-its-you-with-your-company)).

The setup secret is shown only during setup. Marro encrypts the stored secret. Never paste it, a sign-in code or a backup code into Ask Marro or WhatsApp.

## Use a passkey

Give each passkey a name, such as **My phone**. Your browser asks your device to verify you with its fingerprint, face or PIN. Marro keeps the public credential, not your fingerprint, face, PIN or private key.

On the web a passkey is a second step, not a way to sign in on its own (the Marro app can also sign you in with just a passkey, see below): after your password, WhatsApp code, Google or Microsoft sign-in, Marro asks for it and your device verifies you. Passkeys must be configured for the address where you use them. A passkey registered on one address may not work on an organization's different custom domain; use an authenticator or backup code there.

## Signing in

If you have an authenticator or passkey, entering your password or WhatsApp code is the first step. On the web, enter your **Authenticator code**, or open **Try other methods** to switch to a passkey (if available) or backup code. Choose **Sign out** to leave verification. Google and Microsoft sign-in follow the same second-step rule. After company sign-in, Marro skips its own code when your company's identity provider reports it already asked for a second factor (see [Company sign-in](https://docs.marro.si/guides/company-sign-in.md#two-step-sign-in-after-company-sign-in)).

After the second step, you can choose **Trust this device for 30 days** on a private browser. This skips the second step on later sign-ins from that browser; you still need your password, WhatsApp code, Google or Microsoft sign-in. Platform administrators must verify a second step on every new sign-in and cannot use this exception.

The challenge expires after five minutes. Five unsuccessful checks end that sign-in attempt. Repeated attempts against one account are also limited. Start again if the challenge expires.

## Backup codes and lost devices

There are ten backup codes in each set. Marro shows them once and keeps only their hashes. Each code works once. Regenerating a set invalidates every previous code.

If you lose access to all your methods, use a backup code. Otherwise, ask an organization administrator you know to reset your two-step sign-in from **Settings → Sign-in security**. They must verify their own sign-in method first. A reset removes your factors, signs out all your browsers and mobile devices, revokes trusted devices and sends you an email.

A platform administrator with the dedicated recovery permission can reset a recorded organization owner's two-step sign-in from the owner's profile in the platform console. Organization administrators cannot reset a platform administrator's account. Platform administrators should keep backup codes away from their primary device.

## Review and remove access

Your security page lists passkeys with their last use and trusted browsers with their expiry. Verify before removing methods, regenerating codes or revoking devices.

* **Revoke** asks that browser for a second step at its next sign-in. Its existing session continues.
* **Sign out other devices** ends every other web session and every mobile session, and revokes all trusted devices. The browser making the change stays signed in.
* Changing your password invalidates trusted devices and signs out existing sessions through the password-change process.
* Removing the last authenticator or passkey turns two-step sign-in off and invalidates remaining backup codes and trusted devices.

Enabling a factor does not sign out sessions that were already open. Use **Sign out other devices** if you want to end those sessions. Security changes are audited and factor changes, resets and backup-code regeneration generate an email notice.

## Require it for an organization

An organization administrator can enable **Require two-step sign-in** under **Settings → Sign-in security**. The page lists which users have it set up, without showing their methods or secrets.

The grace period is seven days from enabling the organization requirement. Users without a factor are sent to setup on their next web sign-in. After the deadline, they cannot open the CRM until they enrol. Users joining after that deadline must enrol before opening the CRM. Disabling the requirement does not remove anyone's factors.

Platform administrators have no grace period for console access. Their browser session must have completed a real second step; a remembered device or an older unverified CRM session does not grant console access. If the console asks you to sign in again, complete the fresh sign-in and verification to return to the console. A first administrator can sign in with their existing password and open their security page to enrol before entering the console.

## What this protects

An authenticator or passkey adds protection when someone obtains your password or a WhatsApp login code. A sign-in code goes to the account's WhatsApp, or to its email when WhatsApp is unavailable or you ask for email, so someone holding your unlocked phone or your email inbox may receive that first factor. Keep your authenticator, backup codes and trusted browsers secure too.

This does not lock an already signed-in device, protect a compromised browser, add a challenge to every WhatsApp assistant message, or change API-key access. A phone's existing WhatsApp assistant access follows its own number-based checks. Ask Marro can point you to the security page; it cannot inspect or change factors, codes, passkeys, trusted devices or administrator recovery.

## In the Marro app

After your password or WhatsApp code, the app asks for the second step. If you work in several organizations, you choose the organization first.

* **Authenticator code**: type the six digits. The app signs you in on the sixth digit.
* **Backup code**: tap **Use a backup code** and enter one of your codes (`xxxxx-xxxxx-xxxxx-xxxxx`). Each code works once.
* **Passkey**: tap **Use a passkey** and confirm on your phone. You can also tap **Sign in with a passkey** on the first screen to skip the password or WhatsApp code; if you work in several organizations the app then asks which one. If the passkey is cancelled or does not work, the code options stay on the screen.

A wrong code shows how many tries are left. The sign-in lasts five minutes and allows five tries; after that, or when you wait too long, the app takes you back to the first step with a message. After too many attempts on one account, wait 15 minutes. Passkeys on the phone need the latest version of the app.

If your organization requires two-step sign-in and you have not set it up, the app tells you so and opens your security page in the browser. Setting up and managing methods stays on the web; the app never shows setup secrets or backup codes.

Older versions of the app cannot complete a second step. They show a clear message and stay signed out; update Marro, or use the web.


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