> 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/approval-form.md).

# Approval Form

Consent Request Links can be shared by URL link or scanning the generated QR Code.

If included it will display the introduction message upon visit.

<figure><img src="/files/bkzKaHe7glK2k8bsfkdi" alt="Consent Request Link Introduction Brief"><figcaption><p>Consent Request Link Introduction Brief</p></figcaption></figure>

The guest is prompted to enter their Full name and **optionally** their contact details and phone number.

<figure><img src="/files/EUH0KgDOYHnfDLgyJLlC" alt="Consent Request Link User Details"><figcaption><p>Consent Request Link User Details</p></figcaption></figure>

The second step is to upload an existing or capture a self portrait image.

Click **DETECT FACE** button to run [facial recognition](/recognition.md) on the image. This will only be used as data and thumbnail for identifying the person in your HIVO Library.

This image will **NOT** appear as an asset that you can use or share in your HIVO Library.

<figure><img src="/files/JPNnip8d0QQFfcmEHUqB" alt="Consent Request Link Selfie step"><figcaption><p>Consent Request Link Selfie step</p></figcaption></figure>

<figure><img src="/files/PSBUXHb8iW2rgz8I9Vh7" alt="Consent Request Link Upload Selfie"><figcaption><p>Consent Request Link Upload Selfie</p></figcaption></figure>

After running facial recognition. Guest will need to confirm their face was detected correctly.

Click **CONFIRM FACE DETECTED** to continue to consent approval.

<figure><img src="/files/f40OeicFfLPYQXgRUPbv" alt="Consent Request Link Confirm face detected"><figcaption><p>Consent Request Link Confirm face detected</p></figcaption></figure>

The final step is signing a consent form for their approval of the usage terms and terms and conditions provided. If the guest is signing an approval for someone else, they are able to state their full name in the form.

After the guest has agreed on the terms and conditions and signed the approval form they will need to click **SUBMIT** to finalise their consent approval.

This will create a new [Consent](/consent.md) record for the [recognition profile](/recognition.md). A new profile will be created if their profile currently does not exist.

This will also update the Consent status of all the assets in the selected Collections they appear in.

<figure><img src="/files/NUxSv6CMLuMax8AwZTnP" alt="Consent Request Link Consent step"><figcaption><p>Consent Request Link Consent step</p></figcaption></figure>

<br>

<figure><img src="/files/VoXnOnmt4Ek9TSx6axgC" alt="Consent Request Link sign approval form"><figcaption><p>Consent Request Link sign approval form</p></figcaption></figure>

Guest are able to contact support at any stage of the approval form. The form submitted will send a notification to admins that has access to the consent request links.

To edit notification and email subscriptions to this, modify the settings in your profile’s [**Notify Options**](/notifications.md).


---

# 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/approval-form.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.