> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pentaho-data-mastering/setting-up-business-domains/removing-a-business-domain.md).

# Removing a business domain

Remove a business domain when you no longer want to control how the data in that specified category is processed. For example, you might choose to remove one business domain because you want to use a different domain to control the related data elements.

You must have admin privileges to remove a business domain.

Complete the following steps to remove a business domain:

1.  On the left navigation menu, click **Master Data**. The **Master Data** page opens.
2. In the Business Domains card, click **Business Domains**.

   The Business Domain page opens with the business domains shown in a table.
3. At the end of the row that contains the business domain row that you want to remove, click the more options icon and select **Remove**
4. Click **Remove**.

   The Remove Business Domain confirmation box appears.
5. Click **Remove** to confirm that you want to remove the business domain.

   A confirmation message is displayed at the top of the page and the business domain is removed.

   **Note:** If the user selected the **Local** option while creating the business domain, removing the business domain removes all the data related to that business domain from local tables. However, if the user selected the **External Data Source** option while creating the business domain, removing the business domain removes only the internal Postgres tables for that business domain.


---

# 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.pentaho.com/pentaho-data-mastering/setting-up-business-domains/removing-a-business-domain.md?ask=<question>&goal=<user_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.