Asana is where the work lives. Tasks have attached PDFs — briefs, contracts, deliverables. Without discipline, attachments accumulate in tasks and your canonical PDF storage gets out of sync.
Here's the clean pairing.
Asana attachments are pointers, not storage
Attach PDFs to relevant tasks for context, but keep the canonical copy in your file system or Drive. The Asana attachment is a convenience; the canonical lives elsewhere.
When the task closes, the file in your archive is what survives. Asana tasks come and go; archives endure.
Process in Flint, attach the final
Open task attachments in Flint for processing. Save the output to your canonical storage. Update the Asana task to attach the processed version, or link to it.
For signed contracts, signed deliverables, and other 'final' artefacts, attach the flattened, compressed version to Asana so the task tells the whole story.
Use task descriptions for filename references
In the task description, note the canonical filename and path. When someone asks 'where's the signed contract?', the task answers — and not just for the current attachment, but for any future-finding.
A habit worth building: every task with PDF deliverables references the filename in its description.
Archive tasks, archive PDFs
When tasks complete and get archived, the PDFs in your canonical archive are the surviving record. The Asana attachments become reference points, not file storage.
For long-term retention, your file system is the source of truth.
FAQ
Should I store PDFs only in Asana?
No — Asana isn't a permanent file store. PDFs need to live in dedicated storage with proper backup and access controls.
Can I auto-attach Drive files to Asana tasks?
Yes, via Asana's Drive integration. Useful for keeping canonical files in Drive and pointing to them from tasks.
What about Asana's PDF preview?
Useful for quick reference in the task. For real editing, open in Flint.
How do I handle confidential PDFs in Asana?
Private projects with restricted membership. For very sensitive PDFs, keep only links to a restricted storage location rather than attaching the file.
Asana tracks the work; your file system holds the artefacts. Process the next task's PDF in Flint and keep both clean.