> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/command/ja/yzto.md).

# ユーザーと権限

- [ユーザーを管理](https://help.verkada.com/command/ja/yzto/manage-users-in-your-organization.md): オーガナイゼーション'からユーザーを追加、無効化、再有効化、または削除する方法を学ぶ
- [ユーザーとグループ管理のためのディレクトリ](https://help.verkada.com/command/ja/yzto/manage-users-in-your-organization/directories-for-user-group-management.md): ディレクトリを使用して、ユーザーとユーザーグループの管理を分ける方法を学ぶ
- [一時ユーザーを管理](https://help.verkada.com/command/ja/yzto/manage-users-in-your-organization/manage-temporary-users.md): Commandオーガナイゼーション'へのユーザーアクセスを制限する方法を学ぶ
- [Commandグループを管理](https://help.verkada.com/command/ja/yzto/manage-users-in-your-organization/manage-command-groups.md): グループを使用して、ユーザーのサイトとサブサイトへのアクセスを制御します
- [ロールと権限](https://help.verkada.com/command/ja/yzto/roles-and-permissions-for-command.md): Commandユーザーのロールと権限を設定
- [カスタムロール](https://help.verkada.com/command/ja/yzto/roles-and-permissions-for-command/custom-roles.md): Verkada Commandでカスタムロールを作成、設定、割り当てする方法を学ぶ
- [デフォルトロールを変更](https://help.verkada.com/command/ja/yzto/roles-and-permissions-for-command/customize-roles-and-permissions.md): Verkadaの標準ロールの権限を細かく調整する方法を学ぶ


---

# 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://help.verkada.com/command/ja/yzto.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.