Task attachments
Keep supporting files alongside the working brief.
AMS · Connected business workflows
Files & attachments — The file belongs with the work.
Keep supporting material close to the task or record that gives it meaning.
Who this helps
Teammates who need supporting material while reviewing or completing a task.
The situation
A reviewer can find the task but still has to search elsewhere for the proposal and artwork behind it.
Fictional example: the creative brief has an Autumn launch proposal PDF and Collection artwork attachment. This website example makes no live changes.
Follow the example, step by step
Start from the work being reviewed
- What you do
- Open the creative brief rather than starting from an unrelated file list.
- What changes
- The task identifies the work, its owner and its deadline.
- Why it helps
- You know why the supporting material matters.
Keep the proposal attached
- What you do
- Attach the relevant proposal PDF to the task in your workspace.
- What changes
- The sample attachment list shows Autumn launch proposal.pdf.
- Why it helps
- The written scope is available where the review takes place.
Add the visual reference
- What you do
- Include the collection artwork needed to understand the creative direction.
- What changes
- The artwork entry appears alongside the proposal.
- Why it helps
- The reviewer can find both the explanation and the visual material.
Inspect the reference in context
- What you do
- Open a supported preview or use the authorized download option.
- What changes
- The attachment entries provide access to the example files beside the task.
- Why it helps
- You can inspect the material without guessing which work it belongs to.
What your team gains
The person opening the work can find its supporting references in the same task context.
Make the reference material easier to find when someone opens the work.
Inside Files & attachments
Shared previews
Preview supported images, PDFs, documents, spreadsheets, video and audio.
Download access
Retrieve files through the authorized access path.
Workspace storage
Keep uploads within the limits of the workspace plan.
Permission-aware access
Use the applicable file and parent-record controls.
Document outputs
Keep generated documents as part of the wider working context.
Questions and requirements
Does this demonstration upload anything?
No. It uses prepared fictional sample files. Real uploads are subject to workspace storage, upload limits and permissions.
Can everyone preview every attachment?
No. Access follows the applicable file and record controls, and preview support varies by format. A file’s presence does not grant access to unrelated work.
Requirements and limits
Preview support varies by format. Storage and upload limits apply. The website sample does not upload files.
Understand the next tool here
Read how each connection helps before choosing whether to open another page. Moving between tools does not itself configure an automatic handoff.
Documents & PDFs — read how it fits
Generate and review a document before attaching it as a working reference.
Turn reusable templates and variable values into consistent PDF documents.
Fictional example: an Autumn launch proposal receives Forma Studio and 21 October 2026 as its variable values.
Before you use it
Documents are a paid-plan capability. The sample PDF is fictional; it is not a signed agreement or an invoice.
Optional: explore the full Documents & PDFs story ↗Projects & tasks — read how it fits
Keep the files alongside the task’s brief, discussion and next action.
Give every task an owner, a deadline and the context to move forward.
Fictional example: Nour moves the Autumn launch creative brief from In progress to Review.
Before you use it
Available views and actions depend on your access. Time tracking and automations require an eligible paid plan.
Optional: explore the full Projects & tasks story ↗