> 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/commander-17.0.19.md). # Commander 17.0.19 Released on May 14, 2025 {% embed url="" %} ### Improvements `audit-report` When you're logged into Commander with an account that has access to all of the shared folders, you can now execute our "audit-report" command with the Shared Folder UID, and it will generate a report of all events related to that folder, **including ALL events which relate to all records within that folder**. Example: **audit-report --shared-folder-uid XXX --limit 1000 --format table** `import` Improvements to the [CyberArk import process](/keeperpam/commander-cli/command-reference/import-and-export-commands/cyberark-import.md). ### Bug Fixes * Allow user to set special characters for PAM rotation * Suppress team key warning in batch mode * Service Mode REST API bug fixes and security updates * PAM Discovery handling of backend throttling --- # 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/commander-17.0.19.md?ask=&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.