Skip to content

Files & deliverables

The Assets tab in your Home is a place to keep files — images, video, PDFs, spreadsheets, decks, zips, anything — store them once, reuse them across your pages, and hand a client a clean download link.

Open it from the left rail in your Home: Assets.

Click Upload files and pick one or many. There’s no “what type?” — drop in a 2 GB video, a .xlsx, a .pptx, a .zip. Each file becomes a deliverable you can reuse and share.

Files can land in your library from three other places — each records where it came from so the workspace assistant can find it later:

ChannelHowWho
Workspace file inboxEmail attachments to {workspace-slug}@inbox.shareout.siteWorkspace members only — the sender must be signed up with that email
Chat attachPaperclip in the Home Ask your workspace… composerYou (uploads to your scope’s asset bucket)
Share from phoneInstall ShareOut as a PWA, then Share → ShareOut from any appYou — opens Home with the file ready to attach in chat

The workspace inbox address is in Admin → Settings → File inbox (copy with one click). Admins get a bell notification and optional Telegram ping when a member emails files in. Spreadsheets (.xlsx, .csv), decks (.pptx), PDFs, and images are the typical payloads.

Use the folder bar at the top of Assets to group files — client deliverables, brand assets, raw footage, whatever makes sense. New folder creates a folder in the same shared folder tree your pages use; Move on a file tile puts it inside a folder.

Sharing a folder with a client (Admin → Sharing) also shares the files inside it — folders are one tree for pages and files.

Each file is either workspace-visible (default — any member can see and embed it) or private (only you, until you share it). Toggle visibility on a file tile. Private files show a small badge.

  • Workspace-visible files can be embedded in any page in the workspace via a stable file URL (/v1/files/dlv_…/content).
  • Private files are hidden from other members and from anonymous delivery links — share them deliberately via external sharing or Share with a person (below).

Re-sending the third cut of a video? Open a deliverable’s and upload the new file — it becomes v2, v3, and so on. The tile always shows the latest version with a small v3 badge; the clock icon shows the full history, so you can grab an older one anytime.

Open a file’s comments control to leave a thread on that file — same comment system as pages, scoped to the file. Workspace members can comment on workspace-visible files; sharees with a comment grant can comment on files you shared with them.

On a file tile, Share with a person sends a single file to one outside email — no client org required. Pick View or Comment; they get an invite (if new) and the file appears on their /shared portal. Returns 409 if that email is already an internal workspace member — use a normal collaborator invite instead.

On a folder, use Share folder in the folder bar — same flow, grants view or comment on the whole folder (pages and files inside). The share modal lists People you’ve shared with for that file or folder; revoke any grant from there.

External sharees with comment access can leave threads on shared files directly in the /shared portal — see External sharing.

Every asset has a permanent link. Click Copy link on any tile and paste it into a page (an <img>, a button, a download link) — one source, used in as many artifacts as you like. Change nothing on the pages when you swap the file; they point at the same asset.

In artifact HTML, prefer sdk.files.getUrl('dlv_…') for workspace files — it resolves to the latest version and enforces visibility (private files 403 for unauthorized viewers). See SDK: Files.

Editing a page? The visual editor’s toolbar has an Insert asset button — open it, pick a file from your library, and it drops straight onto the page. No copying links by hand.

This is the WeTransfer-style flow:

  1. Click Bundle files to send →.
  2. Tick the files for this delivery.
  3. Create delivery → name it (e.g. “Final files for Acme”). Optionally set an expiry date and protect the link — with a password, or by limiting it to certain email domains (e.g. only @acme.com).
  4. You get a link to a clean, branded download page that lists every file with a Download button.
  5. Copy the link to paste anywhere, or type a client’s email and Send — they get a tidy email with the download link.

Protected links gate the download page and the file bytes — a recipient must clear the password or domain check before any file streams. For a protected delivery, share the /d/<token> link, not the per-file Copy link from the library (that stable URL is for embedding an asset across your pages).

Because it’s a link (not an attachment), file size doesn’t matter — send a folder of 4K renders the same way you send a logo.

Click Sent deliveries at the top of Assets to see every link you’ve minted — collection name, file count, gate type, expiry, open count, and live status (active, expired, or revoked). From there you can copy a link again or revoke it; a revoked link 404s for both the page and the downloads.

The first time someone opens a delivery (past any gate and with the files actually shown), you get an email — for example “Acme opened your delivery.” Repeat opens of the same link stay quiet so a refresh never spams you. For a domain-gated link, the viewer’s email is included in the notification.