> 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/data-migrator/data-migrator-ja/zu-zhi/no.md).

# 組織の概要

## ![](https://1278659608-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvaxzColPOlNbsq4imqpd%2Fuploads%2FcfMTqg4Brbm9baWutclZ%2FSummary2-Small-Icon.svg?alt=media\&token=d1cf162d-c02d-4184-988e-7f7350e450fc) 概要

Organizationsページには、Data Migrator操作で使用可能なすべてのSalesforce orgが一覧表示されます。組織の追加または削除は、Global Settingsアプリから行います。

{% hint style="info" %}

#### 重要

ここにSalesforce orgが表示されない場合は、組織が **Flosum Global Settings** アプリで作成されていること、および **Data Migrator** アプリが各Organizationに割り当てられていることを確認してください。これらの操作の完了手順については、次の記事を参照してください。

* [組織の作成](/global-settings/global-settings-docs-ja/huan-jing/zu-zhi/no.md)
* [組織へのアプリの割り当て](/global-settings/global-settings-docs-ja/huan-jing/zu-zhi/henoapurinorite.md)
  {% endhint %}

<figure><img src="https://1278659608-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvaxzColPOlNbsq4imqpd%2Fuploads%2F9UlFNoUpa1mVkRct6qS8%2FOverviewOfOrganizations-Organizations-01.png?alt=media&amp;token=470895b9-52a7-43bb-bff3-7b26b379c9a1" alt=""><figcaption></figcaption></figure>

Organizationsページにアクセスして利用可能なSalesforce orgを表示するには、左側のサイドバーメニューで **Organizations** をクリックします。orgの一覧は検索でき、orgタイプでフィルターを適用でき、名前または最新のアクティビティで並べ替えることができます。各orgには次の詳細が表示されます。

<table><thead><tr><th width="199.3333740234375"></th><th></th></tr></thead><tbody><tr><td><strong>Organization Type/Name</strong></td><td>Salesforce orgタイプのアイコンが含まれます: <img src="https://docs.flosum.com/~gitbook/image?url=https%3A%2F%2F1800549522-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FRpUu5iMlzMFAudyBvMOl%252Fuploads%252F1AbCztruXPdsPWYQ5SW0%252FConnection%2520Type%2520Production.png%3Falt%3Dmedia%26token%3Ddc87f462-29b8-4fb1-8016-0c6b7649aec0&#x26;width=40&#x26;dpr=3&#x26;quality=100&#x26;sign=7c81d207&#x26;sv=2" alt="" data-size="line"> <strong>本番環境</strong> または <img src="https://docs.flosum.com/~gitbook/image?url=https%3A%2F%2F1800549522-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FRpUu5iMlzMFAudyBvMOl%252Fuploads%252F07WH8T2J8IncQ66fjSzg%252FConnection%2520Type%2520Sandbox.png%3Falt%3Dmedia%26token%3Da2c0b9ba-04df-4ecc-ae3f-5c1868037e72&#x26;width=40&#x26;dpr=3&#x26;quality=100&#x26;sign=9792afb9&#x26;sv=2" alt="" data-size="line"> <strong>サンドボックス</strong>、およびGlobal Settingsで割り当てられたOrganization名。</td></tr><tr><td><strong>ユーザーの氏名</strong></td><td>Salesforce orgとFlosumテナント間の接続を確立するために使用されるSalesforceユーザーアカウントの氏名。</td></tr><tr><td><strong>ユーザー名</strong></td><td>Salesforce orgとFlosumテナント間の接続を確立するために使用されるSalesforceユーザーアカウントのユーザー名。</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/data-migrator/data-migrator-ja/zu-zhi/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.