> For the complete documentation index, see [llms.txt](https://newdocs.keeper.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://newdocs.keeper.io/en/release-notes/backend/backend-api/backend-api-18.1.3.md).

# Backend API 18.1.3

### New Features

* Folder Move (Reparenting): Users can now move folders between locations in their vault, allowing easy reorganization of folder hierarchies within Nested Shared Folders.
* Trashcan Restore: Records and folders sent to the trashcan can now be restored to a specified target folder, with per-item status reporting and full sync support.
* Enterprise Enforcement Policies for Shared Folders: Administrators can now enforce policies that restrict creating records outside shared folders, restrict creating shared folders, restrict removing records from shared folders, and restrict deleting shared folders — all applied consistently across folder and record operations including moves.
* Compliance Reporting for Nested Shared Folder: Compliance reports now distinguish between Drive and legacy records, and include the full Nested Shared Folder permission model in the response payload.
* Record Sharing Notifications: Users now receive notifications when a record is shared with them or when record ownership is transferred.
* Folder Move Audit Logging: Folder reparenting operations are now captured in the audit log for enterprise visibility.

### Improvements

**KA-8646:** Improved the compliance reporting query engine to use parameterized queries instead of dynamic query construction. This improves query plan caching and aligns with best practices for database query handling.

**KA-8144:** Implemented trashcan restore functionality, allowing users to recover deleted records and folders to a specified target folder. 

**KA-8183:** Reduced excessive logging noise caused by repeated warnings during sync operations. Lowered the log severity and removed obsolete registry entries that were flooding operational logs.

**KA-8483:** Added user notifications when a record is shared with them in a Nested Shared Folder context. Affected users and team members now receive a sharing notification.

**KA-8495:** Enforced the enterprise policy that restricts record removal from Nested Shared Folders on the folder record-removal operation. Enterprise users subject to this restriction now receive a clear per-item error, while records in personal folders remain unaffected.

**KA-8496:** Enforced the enterprise policy that restricts Nested Shared Folder deletion on the folder removal operation. Enterprise users subject to this restriction now receive a per-folder error, while non-shared folders remain unaffected.

**KA-8534:** Added user notifications when record ownership is transferred in a Nested Shared Folder context. The receiving user now receives a transfer notification.

**KA-8569:** Fixed the enforcement that restricts record creation to Nested Shared Folders only. Previously the logic was inverted, blocking record creation inside shared folders instead of outside them. Records created without a folder assignment are now also correctly evaluated.

**KA-8570:** Enforced the enterprise policy that restricts record removal from Nested Shared Folders on the record move operation. Moving a record out of a shared folder is now correctly blocked when this enterprise policy is active.

**KA-8571:** Enforced the enterprise policy that restricts shared folder deletion on the folder move operation. Moving a Nested Shared Folders or its subfolders is now blocked when this enterprise policy is active, preventing structural changes that are equivalent to deletion.

**KA-8572:** Enforced the enterprise policy that restricts folder creation to shared folder locations only. Users subject to this policy can no longer create folders in personal locations through the new folder operations.

**KA-8573:** Enforced the enterprise policy that restricts the creation of new Nested Shared Folders. Sharing a previously unshared folder is now blocked when this policy is active, preventing users from working around the restriction.

**KA-8580:** Added audit logging for folder move (reparenting) operations. Nested Shared Folder moves are now recorded in the enterprise audit trail for compliance and tracking purposes.

**KA-8619:** Enhanced compliance reports to distinguish between Nested Shared Folders and legacy records, and to include the full Nested Shared Folder permission model. Clients can now identify record types and render the richer Shared Nested Folder permission set (edit, share, denied, access type, ownership) alongside the existing permission data.

**KA-8624:** Enforced the enterprise policy that restricts Nested Shared Folder creation on the folder move operation. Moving a folder under a shared parent with permission inheritance enabled is now blocked when this policy is active.

**KA-8714:** Fixed trashcan to correctly return removed trashcan records after a restore operation. Restored items now properly appear in the removal list during the next trashcan sync.

**KA-8778:** Improved full sync to exclude access metadata and record metadata for records that have been moved to the folder trashcan.

**KA-8817:** Investigated and fixed the handling of record-level access additions when access already exists. This resolves edge cases surfaced during denial add/removal operations where duplicate access entries could cause unexpected behavior.

**KA-8861:** Upgraded a core networking dependency to address published CVEs as part of our standard update process. This is a security-only upgrade with no functional changes.

**KA-8068:** Users can now move folders from one location to another within their Nested Shared Folder vault. This enables easy reorganization of vault folder structures by reparenting folders and their contents to new destinations.

### Bugs

**KA-8505:** Fixed an issue where creating a folder without explicitly specifying the folder type would be incorrectly rejected. The system now correctly defaults to a normal folder when the type is not specified.

**KA-8521:** Fixed an issue where a classic shared folder record could be incorrectly added to a Nested Shared Folder during a record update. The system now validates record compatibility and blocks cross-model placement.

**KA-8522:** Fixed a permissions issue where users with content and share manager access could incorrectly delete records. Content and share manager permissions no longer grant deletion rights.

**KA-8525:** Fixed an issue where shared folder users were not receiving real-time push notifications after the record owner deleted a record. Clients now receive a push signal so they can immediately reflect the deletion.

**KA-8527:** Fixed an issue where the record expiration setting could not be reset after the expiration duration was changed. Users can now correctly clear or modify the expiration setting on Nested Shared Folder records.

**KA-8533:** Fixed intermittent errors on folder operations caused by concurrent access. The system now gracefully handles contention and returns an appropriate retryable error.

**KA-8542:** Fixed an issue where security score data was empty for Nested Shared Folder records. Security scores are now correctly populated for Nested Shared Folder records.

**KA-8567:** Fixed an issue where full sync returned orphaned data, event history, and stale removal signals for records and folders that no longer exist. Full sync now only includes data for active, accessible items.

**KA-8568:** Fixed an issue where retrying a failed file upload returned an error instead of providing a new upload link. File upload retries now correctly return a fresh upload link.

**KA-8576:** Fixed a session security issue where a record deletion confirmation could be accepted from a rotated session token. Confirmation tokens are now validated against the originating session for consistency.

**KA-8586:** Fixed a server error  during sync that could occur when a user's vault entered an unrecoverable state. The sync engine now handles this edge case gracefully instead of returning an internal error.

**KA-8587:** Fixed an issue where BreachWatch security data was not cleared after a Nested Shared Folder record was deleted. Deleting a record now properly removes associated BreachWatch data.

**KA-8614:** Fixed an issue where removing a Nested Shared Folder to the trashcan was not reflected in the subsequent trashcan sync. Trashed folders now correctly appear in the trashcan sync response.

**KA-8615:** Fixed an issue where PAM configuration records could not be created as Nested Shared Folder records. PAM configuration record creation now works correctly in Nested Shared Folder-enabled environments.

**KA-8618:** Fixed an issue where partial sync was incorrectly demoted to a full sync for users who only had folders and no records. Partial sync now works correctly for folder-only users, ensuring they receive proper removal signals.

**KA-8623:** Fixed an issue where transferring record ownership returned both a classic and a Nested Shared Folder record entry in the sync response for the new owner. Ownership transfers now produce a single, correct record entry.

**KA-8640:** Fixed an issue where permanently deleting a folder did not cascade to its subfolders and grandchild items. Permanent folder deletion now correctly removes the entire folder tree.

**KA-8651:** Fixed a data type mapping error in the Nested Shared Folder access denial filtering logic. This prevents potential incorrect behavior in future access-denial processing.

**KA-8666:** Fixed an issue where setting a non-standard folder usage type on a Nested Shared Folder update was silently accepted but not applied. Invalid folder usage type values are now properly validated and rejected.

**KA-8669:** Fixed server errors and deadlocks when creating Nested Shared Folders under high concurrency for the same user. The system now handles concurrent folder creation requests gracefully.

**KA-8678:** Fixed an error response where an invalid permission inheritance value returned a server error instead of a proper validation error. Invalid input is now correctly reported as a bad request.

**KA-8680:** Fixed an error  where an oversized folder identifier returned a server error instead of a proper validation error. Invalid input is now correctly reported as a bad request.

**KA-8709:** Fixed an intermittent issue where re-sharing a Nested Shared Folder tree could lose child records created by team users after the owner's access was revoked and re-shared. Records created by team members are now properly retained through share revoke/re-share cycles.

**KA-8754:** Fixed an improper access control vulnerability in Nested Shared Folder. Access control checks now correctly enforce permissions for the affected operation.

**KA-8783:** Fixed an issue where trashing or permanently deleting a Nested Shared Folder left orphaned access and sharing state data. Folder trash and empty-trash operations now fully clean up all associated access data.

**KA-8784:** Fixed an issue where moving a record to the trashcan incorrectly removed its access data, which is needed for future restoration. Record access data is now preserved when records are trashed, ensuring correct restore behavior.

**KA-8791:** Fixed an issue where Nested Shared Folder records could not be moved to the vault root. Nested Shared Folder records can now be successfully moved to the top-level vault location.

**KA-8806:** Fixed an issue where BreachWatch security data clearance after record deletion was not communicated to Nested Shared Folder clients. Clients now receive the proper signal to clear BreachWatch data upon record deletion.

**KA-8809:** Fixed an  issue where Nested Shared Folder records could not be moved out of the vault root to a folder. Records at the vault root can now be moved into Nested Shared Folders.

**KA-8834:** Fixed a permissions issue where share admin users could not move records in certain scenarios. Share admin elevation is now correctly applied during record move permission checks.

**KA-8835:** Fixed an issue where restoring a trashed item to the vault root was rejected because an empty target folder was not accepted. Trashcan restore now correctly handles restoration to the vault root.

**KA-8846:** Fixed a server error that occurred during time-limited access expiration when the associated user account could no longer be resolved. The system now gracefully handles this edge case and continues processing the expiration.

**KA-8853:** Fixed a race condition where enterprise policy enforcement for Nested Shared Folder restrictions could incorrectly block record creation immediately after a folder was shared. The system now reads the latest sharing state to avoid false policy violations.

**KA-8855:** Fixed an issue where the contents of trashed folders could not be decrypted because the necessary encryption keys were not included in the sync response.\
Trashcan sync now includes the required keys to allow clients to display trashed folder contents.

**KA-8860:** Fixed an issue where moving a folder left stale parent references, causing the moved folder and its contents to appear under the old location or disappear entirely during a full sync. Nested Shared Folder moves now correctly update all parent references in the sync data.


---

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

```
GET https://newdocs.keeper.io/en/release-notes/backend/backend-api/backend-api-18.1.3.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.