> 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/backend/backend-api/older/backend-api-version-16.2.15.md).

# Backend API Version 16.2.15

## Bug Fixes

* KA-4388: Changing email address in the vault doesn't update immediately on the Console when clicking Sync
* KA-4328: Compliance Report bugs when a record is shared to another Enterprise tenant user.
* KA-4393: Compliance Report needs to include consumer accounts when a record is shared externally.
* KA-4121: Marking a node as isolated from Commander not working
* KA-4425: Previous email verification links are not expiring after generating a new one from changing email address.
* KA-4118, KA-4424: Email rate limiting
* KA-4471: Some users are not found by SCIM GET query

## Improvements

* KA-4304: Added additional helpful security information in the "Share" notifications sent through email. The Record UID, Location and device name of the sender is provided.
* KA-4389: Provide Team/Group Display Name in SCIM user group queries


---

# 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/backend/backend-api/older/backend-api-version-16.2.15.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.