> 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/jp/backend/backend-api/older/backend-api-version-15.1.0.md). # Backend API Version 15.1.0 Released on December 21, 2020 ## Improvements * TRAN-3497: ARAM event added: Enterprise is out of seats * TRAN-3498: ARAM event added: Admin approved a device * KA-3654: Keeper removes pending users when SCIM provider patches user to inactive status * KA3610: Improved performance impacts due to API throttling * KA-3592: Allow Admins to provision invited users into Teams ## Bug Fixes * KA-3625: MSP Keeper Admin is unable to approve SSO Cloud users from managed companies * KA-3560: SCIM email change issues * KA-3615: Broken Access Control - Change permission of other users in the same sharing record * KA-3614: Broken Access Control - Remove user in the same sharing record * KA-3624: Keeper Push fails for Cloud SSO users with DUO enabled * KA-3585: 2FA code duration preference fails for SSO Cloud users * KA-2558: Team folders are not being pushed to users upon login * KA-3637: Unable to login to Web Vault using Alternate Master Password and 2FA * KA-3235: Changed Email Address event isn't displayed in ARAM * KA-3641: Attempting to save empty shared folder record key * KA-3663: Cloud SSO accounts require two Admin approvals --- # 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/jp/backend/backend-api/older/backend-api-version-15.1.0.md?ask=&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.