Deleting documents and folders

​

Deleting a document

Open the document’s ⋮ menu in the sidebar, or right-click it, and choose Delete. A browser confirmation asks Delete "your title"?. Confirm and the row disappears straight away. The web app does not report a failed delete. If the document is still there after a refresh, the delete did not go through.

​

Deleting a folder

Open the folder’s ⋮ menu, or right-click it, and choose Delete. This opens a dialog titled Delete folder. A folder that still contains anything cannot be deleted from the web app. If it holds sub-folders or documents, the Delete button is disabled and the dialog explains why:

“your folder” can’t be deleted because it still contains sub-folders and documents. Move or delete them first.

The wording narrows to just sub-folders or just documents depending on what is inside. Either way, you have to empty the folder first from the browser: move its contents elsewhere, or delete them one at a time. Once the folder is empty, the dialog reads Delete "your folder"? This cannot be undone. and the Delete button is enabled. A connected agent can delete a folder together with everything in it, which is the practical way to clear out a large branch. The agent has to confirm with you first: it reports how many documents and sub-folders would go, and only removes them once you agree.

​

Deletion is permanent from the web app

Behind the scenes, deletion is soft: the record is marked deleted rather than erased, and links pointing at a deleted document dim to unresolved instead of breaking. If the document comes back, those links reconnect on their own. None of that is exposed to you in the browser. There is:

• No trash or deleted-items view.
• No undo, and no toast offering one.
• No restore button anywhere.
• No retention window. Nothing counts down, and nothing is purged on a schedule.

Treat a delete as permanent.

​

Recovering something you deleted

Recovery is possible, but only through a connected agent. Ask the agent to restore the item using the Tatara MCP tools. To bring back a document, the agent calls restore_document with its document id. It goes back to its original folder if that folder still exists, and to the top level if it does not. If something created since has taken its address, it comes back at the next free one. Links that pointed at it resolve again. To bring back a folder, the agent calls restore_folder with the slug or full path the folder had before it was deleted, for example product/pricing. This brings back the folder, its sub-folders, and the documents that were deleted with it, in one call. Restoring a folder never renames it, so it is refused if a live folder now sits at that path, or if its parent folder is still deleted. Restore the parent first.