> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/global-settings/user-management/flosum-cloud-app-permissions/data-migrator-permissions.md).
# Data Migrator Permissions
##  Overview
This article explains Data Migrator app permissions and how they control access to features. Permissions are managed at the Organization level.
{% hint style="info" %}
All users with Data Migrator access can read, edit, and create Templates, and view the history of all Data Migrations.
{% endhint %}
## **Organization Permissions**
Organization Permissions control which actions users can perform on specific organizations. Add organizations individually and select the actions allowed for each. The table below describes each permission.
Permission
Description
Migrate From
Allows users to run a Data Migration with this org as the source, enabling them to copy data from it.
Migrate To
Allows users to run a Data Migration with this org as the target, enabling them to write data to it.
---
# 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.flosum.com/global-settings/user-management/flosum-cloud-app-permissions/data-migrator-permissions.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.