> For the complete documentation index, see [llms.txt](https://docs.ingestlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ingestlabs.com/tag-manager/data-governance/steps-to-add-a-consent-provider.md).
# Steps to Add a Consent Provider
## Introduction
A **Consent Provider** collects, stores, and manages users’ permission for data collection and use.
## Procedure
**Step 1:** Under the Data Governance drop-down, click **Consent Providers.**
**Step 2:** Click on **Add Consent Provider**.
**Step 3:** The **Consent Provider** panel opens from the right side. In the **Name** field, enter the appropriate name. In the **Description** field, provide a proper description.
**Step 4:** Click **Consent Template**. The **Select Consent Template** panel opens. Choose a template from the drop-down list or use the search bar to find and select the required template.
**Step 5:** The selected Consent Template is displayed under the **Consent Template** field. Click **Save**.
**Step 6:** The created Consent Provider is displayed on the screen with the following details:
* **Name** – The name of the Consent Provider.
* **Template** – The Consent Template associated with the provider.
* **Status** – Indicates the current state of the provider.
* **Updated By** – The user who last updated the provider.
* **Updated On** – The date and time of the last update.
{% embed url="" %}
---
# 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://docs.ingestlabs.com/tag-manager/data-governance/steps-to-add-a-consent-provider.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.
