# Backend API 16.11

## Features

* **KA-3754**, **KA-5157**: Support for our new Time-Limited Access feature
* **KA-5689**: Support for new Granular Sharing Enforcements feature
* **KA-5519**: Cloud SSO Configuration shall be node-unique non-shareable across different SSO nodes IF In Use
* **KA-5741**, **KA-5836**: Support for Team Approvals (team creation) via Keeper Automator
* **KA-5628**: Support for Security Key as the only two-factor method
* **DU-352**: Added support for new policy "Disable ability to create duplicate" (DISABLE\_CREATE\_DUPLICATE)

## Bug Fixes

* **KA-5350, KA-5694**: Certain audit event reports which consolidate information are returning too many events. For example:\
  audit-report --report-type=span --event-type=record\_password\_change --column=record\_uid --column=audit\_event\_type --record-uid=\<RECORD\_UID>
* **KA-5438**: Error when deleting a Cloud SSO instance from an empty node tree
* **KA-5692**: If a MSP admin launches into an MC and attempt to perform an account transfer they are getting error “This user is not in a role that has the “Can Be Transferred” enforcement turned on error and cannot complete the transfer.
* **KA-5804**: Support for some hardware security keys that failed due to "invalid size"
* **KA-5769**: Some users receive 400 error on get\_team\_members (viewing team members in the vault user interface)

## Security Updates

* **KA-4055**: Added additional API changes to support server-side verification when a user is prompted for master password re-entry in certain scenarios. This is a low severity finding from Bugcrowd. Releated client tickets VAUL-6192, EM-6185.


---

# Agent Instructions: 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:

```
GET https://docs.keeper.io/release-notes/backend/backend-api/backend-api-16.11.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.