Build features with customer files
Section: DOC-CP-files-data#store-and-serve-user-files.
Let a customer attach a recording to a support request, collect a project's documents, or find a report they uploaded last month. Travila stores the files for the authenticated application user; your application connects each returned file ID to the case, project or other record it belongs to.
Choose the feature you are building
Section: DOC-CP-files-data#start-here.
| Customer need | Recipe and finished result |
|---|---|
| “I need to send you a recording of the bug.” | Build an attachment flow: select a file, confirm the upload, and reopen it from the support request. |
| “Keep this project's documents together.” | Organize project documents: prepare a folder, add documents, and remove the project’s files deliberately. |
| “Find the report I uploaded and mark it reviewed.” | Build a document library: browse, search by name or tag, label work and archive it. |
| “Ask the assistant about this file.” | Attach a file to a conversation: use a stored attachment in a supported model request. |
Connect storage to the signed-in customer
Section: DOC-CP-files-data#how-it-works.
Identify the application user from your authenticated session before making storage requests. Keep a file's ID on your own application record, and request temporary links when that user uploads or opens it. Each user has a separate folder tree and storage quota.
Use folders for organization within that user's files. They do not select another user or create a new authorization boundary. Upload and download URLs are temporary access links; keep them private and store the file ID as the durable application reference.
Prepare your integration
Section: DOC-CP-files-data#related.
Start with authentication so the recipe uses the correct application user. Keep your backend secret out of client-side code. Use the Storage API reference for exact operation fields, response types and supported options as you implement the chosen flow.
Document ID: DOC-CP-files-data. Section identities and revisions.