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

# Organization security policies

> Require two-factor authentication, limit invitations to your domains and review the audit log of sign-ins and security changes in your ProofAge organization.

Administrators set the sign-in rules for everyone who works in their organization under **Settings → Security**, and review what happened under **Settings → Audit log**. These settings are included on every plan.

## Who can manage them

Only **administrators**. Developers and support specialists do not see the **Security**, **SSO** and **Audit log** tabs. Everyone, whatever their role, manages their own [account security](https://docs.proofage.net/console/account-security.md) in their profile, and is bound by the policies below.

A policy applies to work in your organization only. Someone who also belongs to another ProofAge organization is not affected there.

## Require two-factor authentication

With **Require two-factor authentication** on, everyone must sign in with two factors to work in your organization. These count:

* a password with an authenticator code or a recovery code;
* a passkey;
* Google or Microsoft followed by an authenticator code;
* your organization's [SAML single sign-on](https://docs.proofage.net/console/saml-sso.md).

To turn it on, your own current session must have used a second factor; otherwise ProofAge answers "Sign in with two factors first: confirm an authenticator code or a passkey in this session, then try again." This keeps you from locking yourself out.

The section lists the members who have no second factor yet, with their email and role. They are not removed: the next time one of them opens the console, a screen asks them to set up an authenticator app or a passkey before continuing. Someone who has a second factor but signed in without it (for example with only a password) is asked for an authenticator code, a passkey or a [recovery code](https://docs.proofage.net/console/account-security.md#recovery-codes). Recovery codes alone never count: the member needs an authenticator app or a passkey. A member whose email address was never verified verifies it first; the screen sends the email.

The [MCP server](https://docs.proofage.net/integration/mcp/overview.md) and apps connected to ProofAge (such as Zapier) refuse a member who has no second factor at all. Approving a new connection needs a session that meets the policy.

## Allowed invitation domains

**Allowed invitation domains** limits who can be invited: one domain per line, such as `acme.com`. Leave it empty to allow any address.

* An invitation to an address outside the list is refused with "Invitations are limited to: …", whether it is sent by email or as a link, and accepting an invitation sent before the list changed is refused too.
* Matching is exact: `acme.com` does not cover `eu.acme.com`.
* Public mail domains are allowed if you list them.
* Members already in your organization stay; the section lists those outside the list as **Members outside the list**.

## Require single sign-on

**Require single sign-on** is on this tab too, and **Break-glass for administrators** appears under it once it is on. They take effect with a SAML connection and a verified domain. See [Require single sign-on](https://docs.proofage.net/console/saml-sso.md#7-require-single-sign-on-optional).

## Audit log

**Settings → Audit log** lists who signed in and who changed a policy, a key or a member, newest first. Filter it by event, member and dates, and choose **Export CSV** to download the same selection (up to 50,000 rows; narrow the filters for more). Events are kept for 400 days.

| Organization events | Events of a person's own account |
| - | - |
| Member invited, removed, activated, deactivated or role changed | Signed in, sign-in failed |
| Secret key created, activated or deleted | Two-factor code check failed, authenticator code replay rejected |
| Security policy changed (with the old and new values) | Password changed, password reset |
| Domain verified, domain removed | Two-factor authentication enabled or disabled, recovery code used, recovery codes regenerated |
| Single sign-on connection created, updated or deleted | Passkey added or removed |
| Single sign-on refused, with the reason | Sign-in method linked or unlinked |
| | Email address verified, credentials removed after email verification |
| | Session revoked, other sessions revoked |

Each event shows when it happened, the person it concerns, who did it when that was someone else, the IP address and country, and its details. The CSV adds the browser. A change made by ProofAge support shows as *ProofAge support*, without network details.

The events of a person's own account appear for people who are members now, as recorded while they worked in your organization: their activity in another organization stays there. When someone leaves, those events leave your log with them; organization events about them, such as *Member removed*, stay.

Every person sees their own recent events in **Profile → Activity**; see [Your account security](https://docs.proofage.net/console/account-security.md#activity).


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