> For the complete documentation index, see [llms.txt](https://docs.wicle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wicle.io/organization-project/organization-setting.md).

# 組織設定

組織内のメンバー、契約、利用状況を管理します。分析画面のサイドメニューで`プロジェクト / 組織設定`を開き、対象の組織を選択してから、`組織設定`の各画面を開きます。

| 確認・変更したいこと                | ページ                                                                |
| ------------------------- | ------------------------------------------------------------------ |
| 組織名・ロゴの変更、組織の削除           | [組織情報](/organization-project/organization-setting/organization.md) |
| メンバーの招待・権限変更・削除           | [メンバー・招待](/organization-project/organization-setting/member.md)    |
| イベント数・セッションリプレイPV数と使用量の推移 | [利用状況](/organization-project/organization-setting/usage.md)        |
| 契約・支払い方法・使用上限・請求履歴        | [プラン・請求](/organization-project/organization-setting/billing.md)    |
| Wicle AIの有効化とデータの取り扱い     | [AI機能の提供ポリシー](/ai/policy.md)                                       |
| プロジェクト数・アカウント数の上限         | [リミット](/organization-project/organization-setting/limitation.md)   |

契約や組織情報の変更にはOwner権限が必要です。各操作の条件は、リンク先のページをご覧ください。


---

# 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.wicle.io/organization-project/organization-setting.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.