File Control
The File control displays one or more files that you attach when building the template. The user can click a file in the checklist to download it.
Use it to put the material someone needs to do the task right next to the task itself — a procedure document, a form to print, a price list, a floor plan.
File vs. File Upload
The File control and the File Upload control are two modes of the same control, and it is worth being clear which you want:
| File | File Upload | |
|---|---|---|
| Who supplies the file | You, in the template | The user, in the checklist |
| Direction | Download | Upload |
| Read-only in the checklist | Yes | No |
If you want to give the user a file, use File. If you want to collect a file from the user, use File Upload.
Add to the Template
The File control can be added from the controls toolbar in the Template.
Once you have added the control, click Upload File to select a file from your device. The file is uploaded to CheckFlow's cloud storage and appears in the control immediately.
You can upload more than one file to a single File control — repeat the upload to add another. Each file is listed separately in the checklist.
Label
You can set an optional label, displayed above the file list, to describe what the files are — for example Reference Documents or Forms to Complete.
Removing a File
Click the delete button next to a file to remove it from the control.
Use in the Checklist
Each file is shown as a box displaying its file type icon and file name. Clicking a file downloads it.
The control is read-only. Users cannot add, replace or remove the files, and there is nothing for them to fill in — the File control never blocks task completion.
Limits
| Limit | Value |
|---|---|
| Files per control | More than one. Repeat the upload to add another. |
| Maximum file size | No limit imposed by CheckFlow. See the note below. |
| Accepted formats | Any. No file type is blocked. |
CheckFlow does not cap the size of an upload. In practice a very large file is limited by your connection and browser rather than by CheckFlow, and there is no storage quota per checklist or per team.
Notes and Limitations
-
Files are stored in CheckFlow's cloud storage and are downloaded over a secure link.
-
Because the files are part of the template, every checklist created from that template gets the same files. Replacing a file in the template does not change checklists that have already been created.
-
Because it holds no user input, the File control does not appear in Reports, cannot be the source of a Conditional Logic rule, and cannot be used as a Dynamic Value. It can still be shown or hidden by a condition driven by another control.
-
The File control cannot take part in a Linked Checklist control mapping, as either the parent or the child side.
Related Pages
- File Upload — the same control in the other direction, collecting a file from the user.
- Library Files — where to keep a file that several templates need.
- Text — for the instructions that usually accompany a downloadable form.