> For the complete documentation index, see [llms.txt](https://support.hivo.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.hivo.co/faqs/how-do-i-apply-consent-to-an-asset.md).

# How do I apply Consent to an Asset?

To add consent to an asset, create a **Consent Record** for the person shown in that asset: **Add consent from the asset**

#### **🔹** Step 1: Navigate to **Add Consent Record**

* Open the **Asset Detail** page where the person appears.
* Click on the person’s face in the asset.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2F1Gq7yUkMjGzJYYxSMmFv%2FGroup%20821.png?alt=media&amp;token=cdd978b1-6806-4811-abf9-ea7d20670af9" alt=""><figcaption></figcaption></figure>

* Click **More options** to open form "**Add Consent Record"**.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2F7bw5I8mQR8VNMlGvut7Y%2FGroup%20822.png?alt=media&amp;token=021240fd-1d09-4992-9e31-59f799c652db" alt=""><figcaption></figcaption></figure>

#### **🔹** Step 2: **Fill the Consent Record Form**

After clicking **Add Consent Record**, a form will appear. Fill in the following fields:

<table><thead><tr><th width="209.3173828125">Type</th><th>Description</th></tr></thead><tbody><tr><td><strong>Assets</strong></td><td>Select the assets that will be linked to this consent record.</td></tr><tr><td><strong>Status</strong></td><td><p>Choose the appropriate consent status:</p><ul><li>Full Consent</li><li>Partial Consent</li><li>Consent Denied</li><li>Not Applicable</li></ul></td></tr><tr><td><strong>Expiry (Optional)</strong> </td><td>Add an expiry date for the consent.</td></tr><tr><td><strong>Usage Terms</strong></td><td>Select the approved usage terms. <strong>Note:</strong> Admin users can manage/edit usage terms in <strong>Consent Settings</strong>.</td></tr><tr><td><strong>Attachments (Optional)</strong></td><td>Attach files such as scanned consent forms, external documents, or library assets that serve as proof of consent.</td></tr></tbody></table>

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2F3fcimOgBIge7UmegJspm%2FGroup%20823.png?alt=media&amp;token=524faa03-393e-46dc-9f92-c9b507995dab" alt=""><figcaption></figcaption></figure>

#### **🔹** Step 3: **Click “Add Consent”** to save the record

Once you click **“Add Consent”**, the new Consent Record will be saved and attached to the selected person and assets. You can now easily **view, manage, and perform actions** on this record.

Each Consent Record displays the following key details at a glance:

* **Name**: The name of the person the consent relates to.
* **Consent ID**: Unique identifier for the record.
* **Expiry Date**: The date when this consent will expire.
* **Usage Term**: Approved terms under which the assets can be used.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2F5wYq4IgKRFd3OsoqoYWA%2FGroup%20824.png?alt=media&amp;token=1ef4e02e-adea-4838-b81f-72ba428f935f" alt=""><figcaption></figcaption></figure>

See: [**Add User Consent Record**](https://support.hivo.co/consent/add-user-consent-record) and [**Consent Status**](https://support.hivo.co/consent/consent-status)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.hivo.co/faqs/how-do-i-apply-consent-to-an-asset.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.