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

# Commander 18.1.4

Released on Sep 2, 2026

### Highlights

* Improved CyberArk classic imports with richer account metadata retention and more resilient password-retrieval skip handling.
* Added PAM service-management support for COM, DCOM, COM+, and SCOM.
* Improved Nested Shared Folder (NSF) support across PAM workflows and eligible shared-folder discovery.

### Enhancements

* `list-sf --roe-eligible` now includes eligible Nested Shared Folders and identifies each result as `Classic` or `Nested`.
* CyberArk imports support selectively skipping team, role, or user processing with `--skip`.
* PAM service listings now correctly render individual service entries in text output.
* Service Mode treats first-time share invitations as successful, improving automation reliability.

### Fixes

* Fixed NSF-backed PAM records reverting fields after `pam tunnel edit`, `pam connection edit`, and related updates.
* Fixed NSF record loading in `ls`.
* Fixed duplicate Active Directory binding during SCIM operations.

### Security

* Service Mode now blocks access to host filesystem paths, including local-file import/export, and path-based command arguments.
* SailPoint integration is now restricted to documented capabilities. `enterprise-role`/`er`, record ownership transfers, and certain enterprise-user operations are no longer permitted through SailPoint Service Mode integrations.

### References

* [Keeper Commander CLI Documentation](/en/keeperpam/commander-cli/overview.md)


---

# 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://newdocs.keeper.io/en/release-notes/developer-tools/commander/commander-18.1.4.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.
