> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/release-notes/jp/developer-tools/commander/commander-16.11.0.md).

# コマンダー 16.11.0

GitHubでリリースを確認: [https://github.com/Keeper-Security/Commander/releases/tag/v16.11.0](https://github.com/Keeper-Security/Commander/releases/tag/v16.10.11)

## バグ修正

* 所有レコードに関する共有権限の不具合を修正。
* LastPassからインポートした銀行レコードのタイトルが正しく取り込まれない不具合を修正。
* チームメンバーシップ経由のロール情報が以下のコマンド出力に含まれるよう修正。\
  ・`user-report`\
  ・`enterprise-info --users`\
  ・`enterprise-user`
* `share-folder`\
  複数の共有フォルダーのユーザー／チーム／レコードの権限を更新する際に、1つのフォルダの情報が他のフォルダに誤って適用される不具合を修正。


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.keeper.io/release-notes/jp/developer-tools/commander/commander-16.11.0.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.