> 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/editing-the-status-of-a-provider-in-data-governance.md).
# Editing the Status of a Provider in Data Governance
## Introduction
This section explains how to edit the status of a provider under the **Data Governance** module.
## Procedure
To edit the status of the provider under Data Governance, perform the following steps:
**Step 1:** From the left navigation panel, click the **Data Governance** drop-down, and then click **Provider.**
**Step 2:** Click **Edit** to modify the provider’s details.
**Step 3:** From the Status column, open the **Allowed** drop-down menu and select **Blocked** to stop data tracking. You can also change the status back to **Allowed** if you want to enable data tracking again.
**Step 4:** Click **Review** to review the changes before you submit the changes.
**Step 5:** Enter the name in the **Name** field and a description in the **Description** field, then click **Save**. Click **Submit** to submit the changes.
**Step 6:** A confirmation message will appear indicating that the provider’s data has been updated successfully.
**Step Result:** The Provider status is updated in the Data Governance screen as well as in the [Providers](https://ingest-lab.netlify.app/tagmanager/providers/) section.
{% embed url="" %}
[ ](https://ingest-lab.netlify.app/tagmanager/datagovernance/datagovernancescreen/)
---
# 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/editing-the-status-of-a-provider-in-data-governance.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.
