> 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/enterprise/admin-console/admin-console-17.6.1.md).

# Admin Console 17.6.1

This release introduced several new PAM (Privilege Access Management) and EPM (Endpoint Privilege Manager) improvements for large enterprises.

## Features

* **EM-7589** - Improved the sorting for categories and events in the ARAM (Advanced Reporting and Alerts Module).
* **EM-7830** - Added attributes for automation on the Risk Management Dashboard.
* **EM-7714** - Implemented real-time tracking for Gateways.
* **EM-7946** - Added the KeeperPAM guide link to the bottom navigation of the Admin Console.

## Bug Fixes

* **EM-7660** - Fixed the missing step of the "Review the Default Role Policy" in the Role Enforcement Policies settings.
* **EM-7200** - Fixed SSO Connector removal from parent node after editing a sub-node.
* **EM-7925** - Fixed an issue where administrators were unable to remove Nodes under Administrative Permissions.
* **EM-7888** - Fixed an issue on Teams where the filter was not matching the entered characters.
* **EM-7881** - Fixed an issue where administrators do not have the ability to filter by Status on the Roles tab.
* **EM-7876** - Fixed an issue where MSPs can disable PAM (Privilege Access Management) when the MC has users assigned.
* **EM-7734** - Allowed administrators to use \*.com as a domain for the Record Password Role Enforcement Policies.
* **EM-7701** - Fixed the BreachWatch tag showing incorrectly if the customer does not have this enabled.
* **EM-7677** - Fixed an issue where administrators can create duplicate Roles with a space.
* **EM-7617** - Fixed an issue where SMS setup is allowed on free trial accounts.
* **EM-7572** - Improved Active Directory and LDAP Provisioning to ensure the IP address is being validated in the correct format.
* **EM-7479** - Fixed an issue where sub administrators are able to see Users on Nodes that they do not control.
* **EM-6582** - Fixed an issue where administrators are able to move Roles into Nodes that have the same Role name.
* **EM-7643** - Fixed an issue where the subnode can be deleted by the subnode administrator.
* **EM-7951** - Fixed an issue where the Advanced Reporting & Alerts module ("ARAM") report is timing out with over 100K users in the enterprise.
* **EM-7952** - Fixed an issue where the Security Audit report will crash if no changes have been made.
* **EM-7955** - Fixed an issue where a white screen is displayed when creating a new Compliance report.
* **EM-7953** - Fixed an issue where the sorting is working incorrectly on the Security Audit tab.
* **EM-7956** - Fixed a duplication issue with the ARAM Reports showing Activated SCIM twice.
* **EM-7958** - Fixed wording on MSP billing to show correctly on the Endpoint Privilege Manager screen.
* **EM-7959** - Fixed the Endpoint Manager pill to show on the Keeper Administrator Role.
* **EM-7961** - Fixed invalid format errors on the Active Directory Provisioning or LDAP Sync.
* **EM-7968** - Fixed the PAM license validation errors for the MC.


---

# 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/enterprise/admin-console/admin-console-17.6.1.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.