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

# User Agreement

Platform admins can require users to review and accept a custom agreement before they can sign in. This is separate from Airia's own Terms and Conditions and Privacy Policy, which are always presented to users during onboarding.

Navigate to **Settings → Organization → User Agreement** to manage this setting.

## When the agreement is shown

| Option              | Behavior                                                                              |
| ------------------- | ------------------------------------------------------------------------------------- |
| **Off** *(default)* | No agreement is shown during sign-in.                                                 |
| **On registration** | Shown once on a user's first sign-in, and again whenever you edit the agreement text. |
| **On every login**  | Shown on every interactive sign-in.                                                   |

## Writing the agreement text

Author the agreement in the **Agreement text** field using Markdown — headings, bold, italics, links, and lists are all supported. Raw HTML is not rendered.

* Maximum length is 50,000 characters.
* Use the **Write / Preview** toggle to check how the formatted agreement will look before saving.
* There is a single agreement per organization — saving replaces the previous text. Airia does not keep a version history, so keep a copy of prior wording elsewhere if you need one.

## What users see

When the agreement is due, users are shown a **Review and Accept** screen during sign-in with your agreement text rendered below it, along with **Accept** and **Cancel** buttons and links to Airia's Terms and Conditions and Privacy Policy.

* **Accept** lets sign-in continue.
* **Cancel** (or closing the screen) blocks access — the user cannot proceed until they accept.

## Scope

The agreement and its mode apply to your entire organization — every user signing in, including newly invited and reinstated accounts, is subject to the current setting.