Microsoft Teams is your default. SharePoint is your file store. The PDF processing layer is the missing piece. Together with Flint, the three form a clean corporate PDF stack.
Here's how the layers fit.
Teams for collaboration, not storage
Like Slack, Teams is best as the conversation layer. Files dropped into channels live in the channel's backing SharePoint library, but the natural lifecycle treats them as ephemeral chat attachments.
For anything important, file in the proper SharePoint folder, not the chat-attached SharePoint.
SharePoint for structured storage
Mirror your folder structure in SharePoint: `/Archive/<year>/<category>/`, `/Working/<project>/`, `/Templates/`. SharePoint's permission model is corporate-friendly — granular access, audit trails, retention policies.
For regulated industries, SharePoint's compliance features matter more than its convenience features. Lean into them.
Flint for processing
Open SharePoint files in Flint for the work — edit, sign, compress, redact. Flint runs in the browser, so it works on corporate-locked machines without IT approval for a desktop app.
The processed file goes back to SharePoint. Teams gets a link, not a copy.
Share via Teams using links to SharePoint
When you share a PDF in a Teams channel, share the SharePoint link rather than uploading a copy. The recipient sees the canonical version with proper permissions and version history.
This prevents the 'three copies of the same contract' problem that bedevils Teams-heavy workflows.
FAQ
Should I use Microsoft 365's built-in PDF tools?
Edge has some PDF capabilities; Word can convert. For real PDF work — merge, sign, compress, redact — browser tools like Flint are faster.
What about Teams' approval workflows for signed PDFs?
Useful for internal sign-off flows. For external signing, browser tools are simpler.
How do I handle confidentiality in Teams?
SharePoint's permission model handles most. For very sensitive PDFs, password-protect before storing.
Does Teams preserve PDF formatting in chat previews?
Inline previews are basic; clicking opens the full PDF in SharePoint or your default viewer. Don't rely on the preview for review.
Three tools, three layers, one clean workflow. Process your next Teams PDF in Flint and link the result back to SharePoint.