> 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/developer-tools/commander/older/commander-v16.2/commander-v16.2.2.md).

# Commander v16.2.2

Release Oct 1, 2021

## New Features and Improvements

**Edit Role Enforcements**

* KC-272: Enterprise: Edit role enforcements

It is now possible to edit role enforcement policies in Commander. See the [Documentation](/keeperpam/commander-cli/command-reference/enterprise-management-commands.md#changing-role-enforcements-and-privileges) for details.

**Import**

* KC-229: Import/Export Records with Types

Records can now be imported with record types

* KC-286: Import LastPass' Shared Folders

Importing directly from LastPass now shares any shared folders with corresponding Keeper accounts. See the [Documentation](/keeperpam/commander-cli/command-reference/import-and-export-commands/lastpass-import.md) for details.

**Secrets Manager (Beta)**

* Secrets Manager: New format of One-Time token
* Secrets Manager: Added ability to generate config string in Json or Base64.

**Other Improvements**

* KC-122: Title/URL display options in `audit-report`
* KC-259: Fix some account restrictions: Expired Master Password, Accept Account Transfer


---

# 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.keeper.io/release-notes/developer-tools/commander/older/commander-v16.2/commander-v16.2.2.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.