Approve deletion of a knowledge library

Select your mailbox in Complexity and request deleteKnowledgeLibrary. The mailbox must own the library. A group manage share does not authorize complete library deletion. See library ownership.

The tool proposes deletion. Its approval card shows the library name and active file/folder counts. Review them before approving. Deletion cannot be reversed from chat.

Each stage checks knowledge.manage, knowledge.libraries.delete, the separate tool grant, and active MailGen license. It also checks the completed run's original tool selection and active verified Microsoft mailbox ownership. This agent path needs Microsoft setup.

The revision hash includes library metadata, ordered active folders/files, and shares. Execution takes the owner advisory lock and library/folder/file/share row locks. It rereads the snapshot and consumes the single-use approval in the same transaction. Any changed revision rejects deletion.

Canonical human library.delete and writers use the same owner lock. After locking, upload start and folder creation/deletion/rename recheck that the library is active. File rename/retry, library rename, share edits, and ZIP folder import also recheck it. Upload finish returns queued only after a real state transition. Agent writers also serialize under the tenant transaction lock.

Soft deletion hides the library immediately and marks files deleted with cleanupPending. Existing object/vector cleanup removes stored content later. The browser submits stored proposal IDs only. A model or client approved flag is not approval evidence.