> 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/configuring-match-rules/removing-a-match-rule.md).

# Removing a match rule

Remove a match rule that you no longer want to use for controlling how Pentaho Data Mastering identifies matches in the data from different data sources.

You must have admin privileges to remove a match rule.

Perform the following steps to remove a match rule:

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

   The Match Rules page opens with the list of match rules shown in a table.
3. At the end of the row for a match rule record that you want to remove, click the more actions icon and select **Remove**.

   The Remove Match Rule confirmation box appears.
4. Click **Remove**.

   A confirmation notification message is shown at the top of the page and the match rule record is removed from the match rule table.


---

# 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://docs.pentaho.com/pentaho-data-mastering/configuring-match-rules/removing-a-match-rule.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.