# Age verification

Age verification controls the site entry gate for age-gated audiences.

You can use the simple built-in consent dialog or connect AgeVerif for stronger verification flows.

## Configuration

1. Go to `Admin > Settings > Compliance > Age Gate`.
2. Choose the **Site entry age gate** driver: **Disabled**, **Built-in consent dialog**, **AgeVerif client-side checker**, or **AgeVerif backend OAuth**.
3. For the built-in dialog, set the **Cancel redirect URL** used when visitors decline or leave.
4. For the AgeVerif client-side checker, add your **AgeVerif public key**. Optionally limit the allowed AgeVerif challenges, or leave the field empty to use all challenges enabled in AgeVerif.
5. For AgeVerif backend OAuth, add the **OAuth client ID** and **OAuth client secret**, then add the admin-provided callback URL to your AgeVerif Webmaster dashboard.

## Backend OAuth Options

- **Server-side country detection**: choose **None - require everyone**, **Cloudflare CF-IPCountry header**, or **AbstractAPI IP Geolocation**. If you select AbstractAPI, paste your IP Geolocation key.
- **Require verification for**: verify everyone, or only selected countries using ISO 3166-1 alpha-2 codes such as `GB`, `FR`, or `DE`.
- **Require verification when country cannot be detected**: keep this enabled if visitors with unknown countries should still pass the age gate.
- **Minimum age** and **Access cookie lifetime**: set the age requirement and how long successful verification is remembered.

<Info>
AgeVerif portal geolocation applies to the client-side checker. Server-side country detection is used by the backend OAuth driver.
</Info>