> 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/deleting-consent-approval.md).
# Deleting consent approval
In some cases, Guest may reach out to either revoke their consent or advise duplication in submission. Regardless of the reason, admins are responsible for deleting consent approvals when needed. To delete consent approval, follow these steps:
1. Locate the **consent approval record** from the table listed on the Consent Request Link detail page.
* Select Click the **Delete** icon in the corresponding row of the record that needs to be handled.
Consent Request Link approval delete button
👉 If the consent approval led to the creation of a **new person in the Recognition system**, you’ll also have the option to delete that person.
Select whether the consent should be deleted or consent status be updated as *Revoked*.
Consent Request Link approval delete dialog
---
# 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/consent-requests-links-with-qr-code/deleting-consent-approval.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.
.png?alt=media&token=77e4aea6-988a-46f1-8c3d-c73597302641)
