Project Files
Upload, download, and remove files from a project.
Project files keep delivery assets connected to the project where the team uses them.
Use the Files tab as the project handoff surface. Teammates should be able to find current briefs, approvals, deliverables, and reference files without searching chat or personal storage.
Open Project Files
Open Productivity > Projects, select a project, then open the Files tab. The tab shows every file attached to that project.
Use the project Files tab for assets the whole project team may need. If a file belongs only to one task, attach it to the task discussion or mention the task in the filename so the purpose is clear.
Upload a File
Select Upload File and choose a file from your computer. Agiled prepares the upload, sends the file, then attaches it to the project after the upload finishes.
Use project files for assets that belong to the overall project, such as briefs, creative files, requirements, reports, handoff documents, and shared reference material.
Use clear filenames with version or date context when the project will have many
deliverables. A name like Homepage wireframes v2.pdf is easier to review than
final.pdf.
Before uploading sensitive files, confirm the project membership and sharing expectations. A file attached to the project can become part of handoff or review workflows, so internal drafts should be clearly labeled.
Download a File
Use the download action on a file card when you need a local copy. The file opens through the project file download route.
Download the latest version when a file has been replaced. If the team keeps multiple versions, use the filename, upload date, and project comments to confirm which file should be sent to a customer or vendor.
Version Naming
Use filenames that make version and purpose obvious. Include a date, version, or
status when the project has repeated deliverables, such as
Brand guide v2 - approved.pdf or May report - client copy.pdf.
If a file replaces an older customer-facing version, add a project comment or task note explaining which version should be used. This prevents teammates from sharing the wrong attachment later.
Delete a File
Use delete when the file was uploaded by mistake or no longer belongs on the project. Deleting a project file removes the project attachment; keep a copy elsewhere first if the file is still needed.
Before deleting, confirm the file is not referenced in a task comment, document, invoice attachment, customer handoff, or approval thread. If the file is only outdated, upload the replacement and make the current version clear.
Project Files vs Task Files
Use project files for assets that apply to the whole project. Use task comments or task-specific context when the file only supports one action.
During project handoff, review the Files tab and remove duplicates, temporary exports, or internal-only drafts before sharing the project context with a customer or another team.
If a customer needs ongoing access to a file, consider whether the file should also be attached to a document, invoice, ticket, or shared file link. The project Files tab is best for project context; customer delivery may need a more direct sharing path.
Handoff Checklist
Before project handoff or closure:
- Remove duplicate or obsolete drafts.
- Rename vague files.
- Confirm latest deliverables are clear.
- Move customer-facing files to the right sharing path.
- Keep internal-only files labeled or restricted according to your process.