> 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/consent-requests-links-with-qr-code.md).

# Consent Requests Links with QR Code

**Consent Request Links** are special approval forms used to gather consent for all assets in selected collections. This feature is particularly useful for one-time or ongoing events. Simply create a consent request link and using the generated QR code or link, consent can be approved using facial recognition.

### **How to use Consent Request Link**

### **🔹** Step 1: Navigate to Recognition Profile<br>

* Navigate to recognition profile and click on the **Consent Request Links** button:

<figure><img src="/files/IO0JSnQdaGPxoD0RQWFM" alt=""><figcaption></figcaption></figure>

### **🔹 Step 2: View Existing Consent Links**

You’ll be taken to the **Consent Requests with Recognition** page. Here, you can:

* See a list of all existing consent links
* Update or manage them as needed

### **🔹 Step 3: Create a New Consent Request Link**

Click on the **Create Consent Link** button to open the creation form.

<figure><img src="/files/H6ngM1W1GjeT9pGXcZrQ" alt=""><figcaption><p>Create a New Consent Request Link</p></figcaption></figure>

You will be asked to fill in the following:

* **Name** – A clear label for the event or activity (e.g. "Event Shoot May 2025")
* **Start Time** – When the link becomes active
* **End Time** – When the link expires
* **Maximum Number of Entries** – How many people can submit consent using this link

### 👉👉 Learn more about:

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4>Creating a Consent Request Link with QR Code</h4></td><td>Creating a Consent Request Link with QR Code</td><td><a href="/pages/WwNOBrmnsXKHO9mmopyr">/pages/WwNOBrmnsXKHO9mmopyr</a></td></tr><tr><td><h4>Approval Form</h4></td><td>The Consent Request Link consist of a consent approval form with facial recognition</td><td><a href="/pages/XMBYDFp3e0kfMOnSBmBU">/pages/XMBYDFp3e0kfMOnSBmBU</a></td></tr><tr><td><h4>Consent Approvals List</h4></td><td>View consent approvals that have been submitted via a Consent Request Link</td><td><a href="/pages/tSIpNedEh5ntpvvCxrXB">/pages/tSIpNedEh5ntpvvCxrXB</a></td></tr><tr><td><h4>Deleting consent approval</h4></td><td>Remove approved consents as needed</td><td><a href="/pages/Zk8SOKrZqYT3jpAQVi7N">/pages/Zk8SOKrZqYT3jpAQVi7N</a></td></tr></tbody></table>


---

# 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://support.hivo.co/consent/consent-requests-links-with-qr-code.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.