> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/authentication/admin-portal/settings/consent-management.md).

# Consent Management

***

### Overview

The **Consent Management** page lets administrators configure and enforce user consent for biometric authentication (LiveID).

{% hint style="info" %}
**Note:** Consent enforcement is disabled by default for new communities. To enforce it, enable **Require consent before biometric enrollment** and configure a consent document.
{% endhint %}

### When consent is triggered

Users are asked for consent:

* During biometric enrollment (LiveID)
* During login using LiveID, when consent wasn't previously provided **or** the consent document has been updated

### Enable consent enforcement

1. Log in to your tenant as a community administrator.
2. Navigate to **Settings > Consent Management**.
3. Enable **Require consent before biometric enrollment**. Once on, users must read and accept the consent document before continuing with biometric enrollment or authentication.
4. Click **Save**.

### Manage the consent document

The consent document defines what users see and accept.

**Configure the content:**

* **Consent Title** — the title shown to the user
* **Consent Subheading** — an introductory message before the document
* **Consent Body** — the full consent content (supports rich text formatting)
* **Consent Checkbox Text** — the text shown next to the acceptance checkbox

**Preview it:** Use the **Live Preview** panel in the right pane to see exactly how the document will appear to users — it updates in real time as you edit.

**Track what's enforced:** The active document appears under **Currently Enforced**, showing the document name and enforcement date. Any update to the consent document requires users to accept the new version again.

### What users experience

**During enrollment (LiveID):** Users are shown the consent document before biometric enrollment and must accept it to proceed.

**During login:** If consent hasn't been captured, users are prompted to accept it. If the document has changed, users must re-accept the updated version.

### Event tracking

These events are generated for auditing and tracking (see[ Event Logs](/authentication/admin-portal/monitoring-and-reporting.md#event-logs)):

* **E\_BIOMETRIC\_CONSENT\_UPDATED** — the consent setting was updated
* **E\_LIVEID\_CONSENT\_ACCEPTED** — a user accepted consent
* **E\_LIVEID\_CONSENT\_DECLINED** — a user declined consent


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.1kosmos.com/authentication/admin-portal/settings/consent-management.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.