Skip to content

Bulk operations

Doing the same thing to fifty documents one at a time is how mistakes happen. The explorer supports multi-selection and four bulk actions.

In the folder explorer, select documents using the selection control on each card or row. As soon as something is selected, a bulk action bar appears with the count and the available actions.

Clearing the selection or navigating away dismisses it. Selection is per folder view - it does not accumulate across folders as you browse.

The folder explorer with three documents selected and the bulk action bar showing Download, Delete, Move, Copy and Clear selection

The action bar appears with the selection and carries the count, so you can see what you are about to act on.

Moves the selected documents to another folder. Pick the destination from the folder picker.

Moving changes where a document lives, and therefore which folder’s access-control entries and policies apply to it. A document moved into a more restricted folder becomes correspondingly more restricted; a document moved out of one loses that protection. This is the bulk action worth pausing over.

Creates new documents in the destination folder with the same content.

Copies are independent documents. They have their own identity, their own permissions derived from the destination, and their own version history from that point on. Editing a copy does not affect the original.

Because storage is content-addressed, copying does not duplicate the bytes on disk - the copies reference the same stored blob. See Folders and documents.

Soft-deletes the selection to the recycle bin, from which items can be restored to their original location. Nothing is destroyed at this point.

Packages the selection into a single ZIP file.

Documents you lack Download permission on are not included. Content that has not cleared antivirus scanning is not included either. The archive contains what you were actually allowed to have, which may be fewer files than you selected.

A single bulk request is capped at Bulk:MaxItemsPerRequest, which defaults to 200 items. The cap exists so one action cannot tie up a connection long enough to affect everyone else.

For a larger job, work in batches. There is no queued bulk operation that runs in the background - each request completes before returning.

Bulk actions apply the same permission checks as the equivalent single-document action; there is no bulk bypass.

Action Requires
Move Delete on the source, Upload on the destination
Copy Download on the source, Upload on the destination
Delete Delete on each document
Download Download on each document

Where the selection is mixed, the operation applies to the documents you are permitted to act on. Check the result rather than assuming every selected item was included.