Keeping and finding files

Keeping and finding files

What goes in, how it is filed, and what deleting does.

01One place, not three

Pictures, videos and documents all live in the same list. The filters across the top are views of that one list, so nothing can be dropped into the wrong section. Drop a file anywhere on the page and its place is worked out from the file itself.

Images, Videos, Documents
The file by what it is.
Templates
Documents whose text carries merge fields.
Signatures
Signature requests and what came back signed.
Unused
Files nothing references.

02Getting things in

Drop files onto the page, or use Upload in the header. Uploading, generating documents and sending them for signing are permissions of their own, so a role can do one without the rest; deleting belongs to managing storage. Everyone else browses and uses what is there.

03Finding what nothing needs

Every tile says how many places use it, and the Unused filter shows the files nothing references at all. That is the honest list to clear down when storage gets full.

04Deleting

The confirmation names how many places use the file, and those places show a placeholder afterwards. Deleting never cascades. It leaves a visible gap you can fill.

A file a published flow renders from cannot be deleted while that flow is live, because the next run would have nothing to render. Unpublish or repoint the flow first.

Related articles

Where a file is usedHow the platform knows, and why public files load faster.Templates and e-signingMerge field documents and the signing lifecycle.
In this article