> 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/global-settings-docs-ja/yz/flosum-cloud-app-no/data-migrator-no.md).

# Data Migrator の権限

## ![](https://1457003412-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsEk2hU5IMh3HEY5dJZjR%2Fuploads%2FSxcnKlaJKPzDqONWoDNv%2FSummary2-Small-Icon.svg?alt=media\&token=5e3253d0-a069-4ba5-9c06-83c70bd0b21d) 概要

この記事では、Data Migrator アプリの権限と、それらが機能へのアクセスをどのように制御するかについて説明します。権限は組織レベルで管理されます。

{% hint style="info" %}
Data Migrator へのアクセス権を持つすべてのユーザーは、テンプレートの読み取り、編集、作成、およびすべてのデータ移行の履歴の表示ができます。
{% endhint %}

## **組織の権限**

組織の権限は、ユーザーが特定の組織に対して実行できる操作を制御します。組織を個別に追加し、それぞれに許可する操作を選択します。下の表では各権限について説明しています。

<table><thead><tr><th width="200">権限</th><th>説明</th></tr></thead><tbody><tr><td>移行元</td><td>この組織をソースとしてデータ移行を実行できるようにし、そこからデータをコピーできるようにします。</td></tr><tr><td>移行先</td><td>この組織をターゲットとしてデータ移行を実行できるようにし、そこにデータを書き込めるようにします。</td></tr></tbody></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 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/global-settings-docs-ja/yz/flosum-cloud-app-no/data-migrator-no.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.
