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

# Your account security

> Protect your ProofAge console account: sign-in methods, two-factor authentication, passkeys, recovery codes, sessions, recognized devices and security emails.

Everyone manages their own account in **Profile**, whatever their role. Your administrators can [require some of this](https://docs.proofage.net/console/security-policies.md) for work in their organization.

## Sign-in methods

**Profile → Security → Sign-in methods** lists your ways in: linked accounts and your password.

* **Link Google** and **Link Microsoft** add a provider to your account, whatever its email address. ProofAge first asks you to confirm it is you. See [Sign in with Google or Microsoft](https://docs.proofage.net/console/sign-in-with-google-microsoft.md).
* **Link single sign-on for** an organization appears for each organization you belong to that has [SAML single sign-on](https://docs.proofage.net/console/saml-sso.md) enabled.
* **Unlink** removes one. It is disabled when it would leave you with no way in ("Add a passkey or a password first").
* The **password** row changes your password, or sets a first one on an account created with Google, Microsoft or single sign-on.

## Verify your email address

An authenticator app or a passkey can be added only to an account whose email address is verified. If yours is not, **Profile → Security** shows **Send verification email**. Open the link while signed in to this account; it is valid for 60 minutes.

Accounts created with Google, a Microsoft work account or single sign-on, and accounts that accepted an invitation from its email, are already verified. A password reset also verifies the address.

## Two-factor authentication

Two-factor authentication adds a code from an authenticator app (Google Authenticator, Authy, 1Password and the like) to your sign-in.

1. Under **Two-Factor authentication**, choose **Enable 2FA**.
2. Scan the QR code, or type the key shown, into your authenticator app.
3. Enter the 6-digit code to confirm.
4. If recovery codes appear, save them: they come with your account's first second factor (see [Recovery codes](#recovery-codes)).

From then on, ProofAge asks for a code after your password, and after Google or Microsoft. It does not ask after a passkey or your organization's single sign-on: each of those already counts as two factors.

A code works once: the same code cannot be used twice, even within its 30 seconds. After several wrong codes, ProofAge makes you wait before trying again.

**Disable 2FA** asks for a current code from your authenticator app, or, with **Use a recovery code instead**, for one of your recovery codes, which is then used up.

## Passkeys

A passkey signs you in with your fingerprint, face or device PIN instead of a password, and counts as two factors. It cannot be phished.

* **Add passkey** under **Passkeys**; you can have up to **5**. Your password keeps working if you lose a device.
* On the sign-in page, choose **Sign in with a passkey**.
* **Rename** and **Remove** manage them. A browser that cannot create passkeys still lets you remove the ones you have.

## Recovery codes

Recovery codes belong to your second factor as a whole, whether that is an authenticator app, passkeys or both. ProofAge issues **8** of them when you add your account's first second factor, the first authenticator app or the first passkey, and shows them once in a dialog that stays open until you choose **I have saved them**. **Copy all** copies them, and **Download** saves a text file, `proofage-recovery-codes-<date>.txt`, with your account's email address, the date and the codes. Store them somewhere safe, away from your phone and your passkey devices.

Each code works once and is then gone, and ProofAge emails you when one is used, with the number left. A code stands in for your authenticator app or passkey:

* at sign-in, when ProofAge asks for your authenticator code: choose **Use recovery code instead**;
* on your organization's screen that asks you to [prove a second factor](https://docs.proofage.net/console/security-policies.md#require-two-factor-authentication): choose **Use a recovery code instead**;
* in **Profile**, when a change needs your second factor (see [below](#changes-that-need-your-second-factor));
* in **Disable 2FA**, to turn off an authenticator app you no longer have.

Recovery codes alone are not a second factor: an account needs an authenticator app or a passkey to have them.

**Profile → Security → Recovery codes** shows how many codes you have left, warns when 2 or fewer remain, and alerts you when you have none. **Generate new recovery codes** replaces the whole set: the old codes stop working at once. It asks you to confirm it is you and needs your second factor in this session. It is recorded in your activity, and ProofAge emails you about it.

If you only had passkeys before 19 November 2026, your account has no recovery codes yet: generate them in **Profile → Security**. Setting up an authenticator app also issues them.

Turning off your authenticator app keeps your codes while you still have a passkey, and removes them otherwise. Removing your last passkey keeps them while you still have an authenticator app, and removes them otherwise; the next second factor you add then comes with a new set.

## Changes that need your second factor

If your account has an authenticator app or a passkey, these changes need your second factor in the current session: setting up an authenticator app, adding or removing a passkey, and generating new recovery codes. If you signed in with only a password, with Google or Microsoft without an authenticator code, or through your organization's single sign-on, Profile first asks you to confirm with a passkey, an authenticator code or a recovery code, then carries on.

### If you lose your authenticator app or a passkey

* **Lost a passkey:** in **Profile → Security**, remove it and add a new one, or set up an authenticator app. When ProofAge asks for your second factor, use another passkey, your authenticator app or a recovery code. If your account has no password (you sign in with Google or Microsoft), set one first with **Forgot password?** on the sign-in page: removing or adding a passkey also asks you to confirm it is you, and a recovery code does not replace that confirmation.
* **Lost your authenticator app** (for example a new phone):

  1. Sign in with a recovery code: **Use recovery code instead**.
  2. In **Profile → Security**, choose **Disable 2FA**, then **Use a recovery code instead**, and enter another code.
  3. Choose **Enable 2FA** and set up the app on your new phone.

  If the app was your only second factor, the dialog warns that your recovery codes stop working when you turn it off; setting the app up again gives you a new set of 8. If you also have a passkey, your codes stay as they were, and **Enable 2FA** first asks you to confirm with the passkey or one more recovery code.

Keep at least one recovery code: with no second factor device and no code left, you cannot get back in on your own.

## If you forget your password

**Forgot password?** on the sign-in page emails you a reset link. A reset keeps your authenticator app and your passkeys, and ProofAge asks for them as usual afterwards.

If your email address had never been verified, the reset verifies it and also removes linked Google, Microsoft and single sign-on accounts, and signs out every session and connected app: whoever holds the mailbox keeps the account.

## Sessions

**Profile → Sessions → Active sessions** lists where your account is signed in: browser, system, IP address, country and how you signed in (for example *Password + authenticator app* or *Google*). **This device** marks the one you are using.

* **Revoke** signs out one session.
* **Log out other devices** signs out all the others.

Both ask you to confirm it is you.

## Recognized devices

**Profile → Sessions → Recognized devices** lists the browsers your account knows. ProofAge emails you when you sign in from a browser it has not seen before, but never about these, and never on your very first sign-in.

**Forget** signs that browser out, and the next sign-in from it counts as new. A device not used for 90 days is forgotten automatically, and an account keeps at most 20, the least recently used going first.

## Activity

**Profile → Activity** lists your own sign-ins and security changes of the last 90 days: successful and failed sign-ins, password and two-factor changes, passkeys, linked accounts and revoked sessions. Your administrators see these events in their [audit log](https://docs.proofage.net/console/security-policies.md#audit-log) too.

A session opened through your organization's single sign-on works in that organization only, and does not show the **Sessions** and **Activity** tabs. Sign in with your own account to use them.

## Security emails

ProofAge emails you when something changes about how you sign in:

| Email | When |
| - | - |
| New sign-in to your account | A sign-in from a browser your account does not recognize. |
| Google / Microsoft / Single sign-on (SAML) sign-in was added to your account | A provider or single sign-on was linked, by you or automatically by email. |
| Your password was changed | The password was changed in your profile. |
| A password was set on your account | An account without a password got one. |
| Your password was reset | A reset link was used. |
| Two-factor authentication was turned on / off | The authenticator app was set up or removed. |
| A recovery code was used to sign in | With the number of codes left. |
| New recovery codes were generated | The old codes no longer work. |
| A passkey was added to / removed from your account | With the passkey's name. |

Each one says when and from where it happened, and what to do if it was not you: reset your password, review your sign-in methods or sign out your other devices.

The same kind of email is sent at most once in 10 minutes, and password-change emails go only to a verified address.

Unlinking a sign-in method, signing out sessions and failed sign-in attempts are not emailed; they are in **Profile → Activity**.


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