# Do files attach to records one at a time, or as folders?

> Linking a single file to a record is trivial. Keeping a whole folder in step with a record as both change is a different problem, and this page draws the line between them.

*Buyer's guide · Question 3*

## One file, or a *folder*?

Linking a single document to a record is trivial. Keeping a whole folder in step with that record, as both change, is a different problem.

For Salesforce admins and whoever is scoping the actual requirement, not just the demo.

Last verified 21 Aug 2026·Sources: CloudFiles documentation·v1.0 Where this claim comes fromPublished by CloudFiles, who build the folder automation described below. It's drawn from our own published tutorial, not a third-party document the way the storage and Files Connect pages are, so verify it against your own sandbox before relying on it.

## Why folders are a different problem
Linking one document to one record is a solved problem; every tool in this category does it. A folder is not one thing, it's a container whose contents change independently of the record.

Keeping it “in step” means: a file added or removed externally shows up on the record without anyone doing that by hand; the folder itself is created, and ideally named and located, to match the record automatically; and a change to the record, a rename, a stage change, a reparenting, doesn't silently orphan the folder from what it's supposed to represent.

## What CloudFiles does here

- An admin builds the folder hierarchy **once**, using a documented Flow-action tutorial (Create Folder, configure destination, create sub-folders); it then creates that hierarchy automatically **per record** from then on.
- The hierarchy shape (flat, or nested by object/field) is set during that one-time build, not per record.
- Folder creation is one of the automations covered by [the automation-and-failure page](/salesforce/document-management/questions/automation-and-failure-handling), including what happens when a step in that chain fails.

Source: [Create Automated Folder Hierarchies for Managing External Files from Salesforce Objects](/salesforce/create-automated-folder-hierarchies-for-managing-external-files-from-salesforce-objects). Retrieved 21 Aug 2026.

## What to ask any vendor

- Does renaming or reparenting the record rename or move the folder, or does the link quietly drift?
- If folder creation fails partway, is that visible to an admin, or does the record just end up with no folder?
- Can the hierarchy be reorganized later without breaking the record-to-folder link for files already filed?

## What your answer means
**Single documents only,** nothing that needs to stay organized as a set: skip folder tooling entirely. A basic link or attachment on the record is enough, and it's free.

**Folders that need to track a record as both grow and change:** this becomes a real requirement. Ask for a live demonstration against your own record types, not a description of the feature.

## Where this stops
This page settles the file-versus-folder distinction only. Automation reliability is its own question, and identity is a separate one; both are elsewhere in [the guide](/salesforce/document-management/guide#questions).

## *Check* my working

Most readers won't need this. If your folder requirement is unusual, say what's in the way.

- Report: written assessment, two to three working days.
- Reader: a person. Not a bot, not an auto-reply.
- Call: only if you ask. We won't ask twice.
- Fields: four. No phone, no company size, no mailing list.

**What happens next**

One chip, one line, one email.

A contact form follows this section.

Last verified 21 Aug 2026·Reviewed quarterly·v1.0