Delete provider files and object folders

Review recursive scope, permanent removal, and per-item outcomes in the file browser.

Deleting provider files acts on the stored objects in the selected connection. It is different from deleting a Data source's output records, closing a document viewer, or removing a connection credential.

Choose the browsing view

The object-store browser can show Folders or All objects. Folders shows the immediate hierarchy. All objects shows the recursive files under the current location with names relative to that location. The folder breadcrumb remains relevant in both views.

Use the recursive view when you need to inspect nested objects before selecting a destructive scope. The current folder and view survive a reload, and returning from an opened document preserves that browsing context.

File and folder selection

Select individual files when you want a narrow deletion. A selected folder represents a prefix and can contain objects you have not opened or loaded individually. A selection containing folders requires the stronger typed confirmation described in the dialog.

Check the full folder path and connection before typing the confirmation. Two folders with the same last segment can have different scopes. Cancelling leaves the objects unchanged.

Interpret the report

Deletion can partly succeed. Inspect each result instead of assuming a completed request means every object was removed. An already missing object is not an error requiring restoration; it is already in the requested absent state. Failed or uncertain items need investigation before retry.

Object deletion has no Strive trash or automatic undo in this experience. A recursive prefix operation can continue over multiple pages, so the currently visible rows do not define its entire impact.

Cloud storage transfer cleanup follows additional safeguards and can retain source folders. See Storage folder operations rather than assuming every provider uses object-prefix deletion rules.