> 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/consent/edit-multiple-consents-record.md).
# Edit Multiple Consents Record
Adding multiple Consent Records for different individuals proves useful for example: when an existing Consent file already encompasses their respective consents.
The **Edit Consent** feature allows you to:
* Update the **consent status** for multiple assets at once.
* Create a **new Consent Record** including related people, attachments, usage terms, and more.
* Override the previous Consent Record on the selected assets.
This is especially useful when you need to update consent for several individuals or when a single consent file applies to multiple assets.
⚠️ **User Right Required:** You must have the **“Can Edit Consent”** permission to perform this action.
## **How to edit M**ultiple Consents Record
#### **🔹 Step 1: Select Asset**
* Navigate to the **Library** from the left-hand menu.
* Select the **assets** you want to update.
#### **🔹 Step 2: Open Action menu and select "Edit Consent" option**
* Click the **Actions** button at the top or bottom of the screen.
* Select **Edit Consent option**
#### **🔹 Step 3: Fill in the New Consent Record**
A **Consent Record** form will appear. Fill in the following fields:
* [**Consent Status**](https://support.hivo.co/consent/consent-status)**:** Choose the consent status for the assets:
* Full Consent
* Partial Consent
* Consent Denied
* Not Applicable
* **Expiry:** Specify the consent expiration date (if applicable).
* **Usage Terms:** Approved usage terms for the asset. Admins can manage these terms under **Consent Settings**.
* **Related People:** List the individuals related to the selected assets (e.g. models, people appearing in content).
* **Attachments (optional):** Attach supporting documentation such as:
* PDF files
* External links
* Other assets from the Library.
📌 **Note:** All details entered will apply to **every asset** and **related person** selected.
If you have any questions, don't hesitate to ask, we're always here to help!
---
# 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/consent/edit-multiple-consents-record.md?ask=&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.
