Skip to main content
Back to Resource Guide
Jun 9, 2026

Batch Upload Collections: Share Multiple Files with One Link

Learn how signed-in users bundle installers, design assets, and document sets into a single collection link with optional ZIP download.

Collections
Batch Upload
Workflow

Learn how signed-in users bundle installers, design assets, and document sets into a single collection link with optional ZIP download.

  1. Name the file clearly before upload.
  2. Preview the share page before sending it externally.
  3. Add a password when the file contains customer, account, contract, or operational data.
  4. Choose an expiry window that matches the real review period.
  5. Use copy-all handoff text when the recipient needs link, password, and expiry details together.

Make one collection mean one thing

Create a collection for a single delivery, review, onboarding package, or incident. Avoid mixing unrelated files just because they were ready at the same time. The collection title should identify the recipient, purpose, and version so that a download folder remains understandable after it is saved locally.

Put files in a usable order

Use consistent names such as 01-readme, 02-installation, and 03-assets when the recipient needs to follow an order. Include a short readme for packages with setup steps, assumptions, or required passwords. Before sharing, preview the collection as a recipient and confirm that the expected files are present and no draft or duplicate file slipped in.

Maintain one source of truth

When a file changes materially, replace the collection with a clearly named revised version and tell recipients which package to use. Leaving several files called final, final-2, and really-final makes the collection less useful than an ordinary attachment thread.

Plan the recipient's first five minutes

Arrange a collection so a recipient can orient themselves without asking for clarification. Start with a readme or overview, then use predictable prefixes for files that must be opened in order. State prerequisites, expected output, and the owner of the package. Do not include drafts, personal working files, or unrelated assets merely because they are nearby in the source folder.

Apply controls at the right boundary

One collection should have one audience and one retention expectation. If a package mixes public artwork with confidential commercial terms, split it into separate shares instead of applying the same password and expiry to both. Before delivery, inspect the collection from a recipient's point of view and confirm that every included file is intentional.

Revise without creating version confusion

When a delivery changes, create a replacement collection with a versioned title and a short change note. Tell recipients which collection supersedes the previous one and let the previous share expire when practical. This preserves a clear audit trail while ensuring a new recipient does not download an obsolete installer, document, or asset set.

Practical workflow

Before creating the share

Prepare the smallest useful version of the material first. Use a descriptive filename, confirm that the recipient is allowed to receive it, and decide the review deadline before selecting password, expiry, or download controls. Then open the completed link in a private browser window so you see the same prompt and preview that the recipient will see.

Collections are for a coherent delivery set, not a replacement for a drive full of unrelated files. A recipient should be able to identify the purpose and the correct order of the files from the title alone.

Decide before you send

  • Group files by one review, client delivery, or incident instead of mixing unrelated work.
  • Use predictable names and include a short readme when the receiver needs an order of operations.
  • Apply the same access policy to the entire collection only when every file has the same sensitivity.

After the handoff

Download or preview the collection as a recipient before sending it. Replace superseded files rather than leaving multiple final versions for others to guess between.

Back to Resource Guide
Batch Upload Collections: Share Multiple Files with One Link