# Backend API Version 14.5.0

## New Features & Benefits

**Node Isolation Option for MSP Customers**\
\
The Keeper Backend now as the ability to enforce Node Isolation for business customers. When "Node Isolation" is activated, users and teams that show within Share screens on the vault are limited to parent and child nodes. This feature is built for MSP customers who configure each node in the Keeper Admin Console as a separate end-customer account.\
\
In the example below, if Node Isolation is activated on the West Coast node then:\
\
Users in "**Developers**" are able to see other users and teams up in Developers, West Coast, Regions, Engineering and Craig Lurey LLC.\
\
Users in "**Developers**" are **NOT** able to see the users and teams in "**East Coast**" or "**Sales**", since those nodes are in parallel tree paths.

![Node Isolation Example](/files/-LdQDD_uO7kJeYb-asHt)

On the Vault, the screens affected by this change are the "Shared Folder" and "Record Share" screens:

![Shared Folder Permissions Screen](/files/-LdQFT-J4WG-qdqzpXIJ)

![Record Share Screen](/files/-LdQFWpkn9D90qRpD6m6)

{% hint style="info" %}
To activate Node Isolation please contact us <https://keepersecurity.com/support.html>
{% endhint %}

### Other Improvements

* Migrating from Google Cloud messaging (GCM) to Firebase Cloud Messaging (FCM) for Android platforms.<br>
* During Vault Transfer / Account Transfer, team permissions are also transferred now.<br>
* Optimization for syncing a large number of folders and records, when team permissions and individual user permissions overlap the same records. Duplicates are removed from the sync down response which decreases the overall encrypted package size.<br>
* Created an optimized "import" backend API for record import

## Bug Fixes

* Fixed "record key already encrypted with datakey" error which occurs randomly<br>
* German translation improvement (backend errors and success messages)

## Coming Soon

The next Backend API 14.6.0 release will support BreachWatch for Business.


---

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