Notion holds your team's brain — projects, docs, knowledge. PDFs that arrive into Notion-shaped workflows need processing somewhere else, then linking back. Flint handles the processing; Notion handles the context.
Here's the pattern.
Notion for context, not for PDFs
Notion's PDF embed is fine for viewing but limited for editing. Treat Notion as where the PDF is referenced and discussed, not where it's manipulated.
Each project page in Notion has a 'Documents' section that links to the actual PDFs in your file system or cloud storage.
Process in Flint, link from Notion
When a PDF needs work — sign, merge, compress — open it in Flint, do the work, save the output. Update the Notion link to point to the processed version.
Don't store working PDFs in Notion. Store finished PDFs (or links to them) once the work is done.
Embed final PDFs for inline reading
For PDFs that need to be readable in the project context (signed contracts, completed deliverables), embed them in Notion via the file block. Notion shows a preview that opens to the full PDF on click.
For large PDFs, link rather than embed — Notion can struggle with very heavy embeds.
Search across Notion plus file system
Notion's search finds the link or embed; your OS search finds the file. Together they cover the discovery loop.
Keep filename and Notion page title consistent so search works whichever side you start from.
FAQ
Can Notion handle signed contracts as the canonical store?
Not ideal — Notion isn't designed for document permanence. Keep contracts in a file system or dedicated contract store; reference them from Notion.
What about Notion's commenting on PDFs?
Useful for discussion threads referencing the document. Real edits happen in the PDF itself via Flint.
How do I avoid duplicating PDFs between Notion and storage?
Pick one as canonical (usually file system) and one as reference (Notion link). The discipline matters more than the tool choice.
Does Notion preserve PDF version history?
For embedded files, Notion keeps the version you uploaded. If you replace it, the old version is overwritten. Keep version history in your file storage instead.
Notion is context; Flint is processing. Use each for what it's built for. Process your next PDF in Flint and link it back to Notion.