> 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.11.3.md).

# Admin Console 17.11.3

Released October 14, 2026

## Overview

Admin Console 17.11.3 introduces user interface support for Node Isolation, new Role Enforcement Policies for Passkey Authentication controls, and Endpoint Privilege Manager enhancements, alongside improved SCIM team visibility and critical Government Cloud bug fixes.

## New Features

### Node Isolation

We've added the ability to enable or disable Node Isolation directly from the Admin Console under **Admin > Node Options**, allowing you to restrict visibility between sibling nodes without requiring commands to be run through the Keeper Commander CLI.

<figure><img src="https://1549319098-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LSGErxSfzX6xZALob42%2Fuploads%2Fm7EkGxyr80S83Woa2uEC%2FGroup%2036149.png?alt=media&amp;token=f86e35a1-da0f-4179-8b50-aa6bd8d38efe" alt=""><figcaption><p>Node Isolation Setting</p></figcaption></figure>

### Passkey Authentication Role Enforcement Policies

Added Enforcement Policies to control whether Passkey Authentication is enabled and specify which authentication methods users can use, including security keys and biometrics.

<figure><img src="https://1549319098-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LSGErxSfzX6xZALob42%2Fuploads%2Fi2jjp9yzUdBzQnj8OzoZ%2FGroup%20330.png?alt=media&amp;token=72e06982-1b9d-44a3-a708-e7fd34d94fcd" alt=""><figcaption><p>Passkey Authentication Enforcement Policies</p></figcaption></figure>

## Improvements & Bug Fixes

* **EM-9118** - Added a Keeper 101 Video on the "Getting Started" page for KeeperDB.
* **EM-9159** - Added a search filter to Nodes for easier navigation.
* **EM-9082** - Added an "Invited" tab to Teams to display SCIM-provisioned users who have not yet accepted their invitation.&#x20;
* **EM-8795** - Added an error message when creating a Role or Team name that goes over the maximum amount of characters.
* **EM-7773** - Added the edit option after verifying and saving Email Auto-Provisioning.
* **EM-9146** - Added tooltips to all the KeeperPAM Enforcement Policies.&#x20;
* **EM-9104** - Improved the User Status Report download filename to include the report name and date.
* **EM-8761** - Fixed an issue where newly created Roles were not automatically selected by default upon creation.
* **EM-8680** - Fixed an issue with the Government Cloud environments showing the Risk Management Dashboard scores not tabulating for certain users.
* **EM-8327** - Resolved an issue where the BreachWatch section is not appearing on the dashboard for Managed Companies.
* **EM-8472** - Fixed an issue with Endpoint Privilege Manager where custom policy types were not sorted correctly.
* **EM-8970** - Fixed an issue where the "Stay Logged In" toggle was not working correctly after a page reload.
* **EM-9226** - Fixed an issue where a Managed Service Provider could not download a Compliance Report for a Managed Company.
* **EM-9191** - Fixed the Endpoint Privilege Manager Deployment token domain for Government Cloud environments.


---

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