> 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/modifying-rules-roles-and-data-sources-in-bulk.md).

# Modifying rules, roles, and data sources in bulk

Modify multiple rules, roles, and data sources at one time by exporting a JSON file and\
editing the information in the JSON file.\
Perform the following steps to modify rules, roles, or data sources in bulk:

1. In a table that contains rules, roles, or data sources, select checkboxes for one or more rows of data that you want to modify.
2. At the bottom of the table, click **SELECTED**.
3. Click **Export**.
4. Enter a name for the JSON file and click Continue.
5. In the **Match Rules Exported** dialog box, click the download link to download the exported JSON file. The JSON file is downloaded to the location that you specify.
6. Click **Close**.
7. In a text editor, update the data in the JSON file.
8. Save the JSON file.

**Next steps**\
To add the updated rules, roles, or data sources that are in the JSON file to the application, complete one of the following procedures:

* [Adding match rules in bulk](https://docs.pentaho.com/pentaho-data-mastering/configuring-match-rules/adding-a-match-rule/adding-match-rules-in-bulk.md)
* [Adding merge rules in bulk](https://docs.pentaho.com/pentaho-data-mastering/configuring-merge-rules/adding-a-merge-rule/adding-merge-rules-in-bulk.md)
* [Adding user roles in bulk](https://docs.pentaho.com/pentaho-data-mastering/setting-up-users-and-roles/adding-user-roles/adding-new-user-roles/adding-user-roles-in-bulk.md)
* [Adding data sources in bulk](https://docs.pentaho.com/pentaho-data-mastering/sourcing-data/adding-a-data-source/adding-data-sources-in-bulk.md)


---

# 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/modifying-rules-roles-and-data-sources-in-bulk.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.
