To put a file on a client's profile, you upload it to your main Vault first, then assign it to the client from their profile's Vault → Files tab. Fitsly does not yet have a "drop a file straight onto this client" option — the two-step Vault flow is the only supported path today.
Steps
- Sign in to
app.fitsly.comon a desktop browser. - Click Vault in the left navigation to open your main Vault.
- Click New (or the equivalent add button at the top of the Vault) to open the Create vault item modal.
- With the Upload tab selected, drag your file into the drop zone or click to browse. Supported file types: images, videos, PDFs, documents, text, and audio. Maximum file size is 300 MB.
- Give the vault item a recognisable name (e.g. "Medical clearance — [client first name]") and tag it if you use tags. Save the item.
- Open Clients in the left navigation and click the client you want to attach the file to.
- Click the Vault tab in the client profile. Switch the inner toggle to Files (the other inner option is Collections).
- Click the add button to open the resource picker.
- Select the file you just uploaded and confirm. The file is now assigned to that client and visible to them in their app's Vault.
If you need a folder of files for one client
If you have several files that belong together (medical history, intake docs, contract), build a Collection in the main Vault first, add the files to that Collection, then assign the Collection to the client from their Vault → Collections tab using the same picker. The client sees one tidy folder instead of several loose files.
If the file is for internal use only (not for the client to see)
Coach-only file storage on a client's profile isn't supported yet — every file you assign through the Vault flow above is visible to the client in their app. The workaround is to upload the file somewhere external (Google Drive, Dropbox, OneDrive, etc.) and paste the shareable link into a private coach note on the client's profile.
- Open the client's profile and stay on the General tab.
- Click the Goals & Notes pill in the inner menu (next to Overview, Profile, and Pinned Notes).
- Scroll to the Notes section. The heading reads "Notes (private)" — anything you add here is visible to you only, not to the client.
- Click to add a new note and paste the Google Drive (or other shareable) link into the note body, with a short description of what it is. Save the note.
The link sits on the client's profile for your reference and the client never sees it. Replace this workflow with the native Vault assignment flow above whenever the file is meant for the client to view.
What about chat attachments?
The chat composer in Messages lets you attach photos and videos only — there is no option to send a document or PDF through chat. The Paperclip icon ("Add media" tooltip) opens a menu with only Add photos and Add video. For anything that isn't a photo or video, use the Vault flow above.
Things to watch out for
- There is no "Files" or "Attachments" section on the client profile outside of the Vault tab. If you're hunting for one in General, Forms, or anywhere else on the profile, you won't find it.
- Pinned notes do not currently support attachments. Notes are text-only — pair the note with a Vault file if you need to reference a document.
- The 300 MB file-size limit applies in the Vault. Uploads above that size are rejected with the toast "File size exceeds 300MB limit."
- Unsupported file types (e.g. executables) are rejected with the toast "Unsupported file type. Please upload an image, video, or document."
- Files assigned via the client's Vault tab are visible to that client in their own app — they're not coach-only. For internal-use files, use the Google Drive link workaround in the Goals & Notes → Notes (private) section above.
- The Vault → Files sub-tab inside the client profile only shows files that exist in your main Vault. If you can't see a file in the picker, it hasn't been uploaded to the main Vault yet — go back to step 2.
- Direct upload from the client profile is on the roadmap. Until it ships, the Vault-then-assign path is the only working option.