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

# Portal logins and security codes

> How to save a portal login, how Alder stores it, and what happens when a portal asks for a code.

## Save a portal login

An owner saves a login for each customer portal: the username, the password and, if the portal uses an authenticator app, its setup key.

* Logins are **encrypted** before they’re stored (AES-256-GCM).
* Nobody can read a saved password back, including your team.
* Only Alder’s browser uses the password. Alder’s AI model, its logs and its activity history never see it.

> [!NOTE]
>
> Portals that send you to single sign-on on a different domain aren’t supported yet. Tell us during onboarding if a customer uses one.

## Security codes

When a portal asks for a code, Alder tries in this order:

**1. Authenticator setup key**

If you saved the portal’s authenticator setup key, Alder generates the code itself.

**2. Your AR mailbox**

Otherwise Alder checks the connected mailbox. It uses a code only if exactly one fresh code from that portal arrived in the last 15 minutes.

**3. A person**

Otherwise Alder asks you, in the app or in Slack. Enter the code there. Alder waits up to 20 minutes.


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