Microsoft Teams PDF library
This guide outlines two approaches to integrating PDF capabilities within Microsoft Teams using SharePoint. Choose the approach that fits your team’s needs — instant and powerful with no code, or fully customizable with full-stack flexibility.
No-code PDF viewer and editor
The no-code option is perfect for business users and teams that want powerful PDF viewing and editing capabilities inside Microsoft Teams without writing a single line of code.
Key capabilities
- PDF viewing and navigation
- Text editing
- Annotation (highlight, comment, stamps, shapes, and more)
- Form filling, creation, and submission
- Signatures
- Page manipulation (add, remove, rotate, crop, move, copy)
- Merging PDFs
- Redaction and security tools (for example, adding watermarks)
- Measurement tools and link insertion
Prerequisites
- Nutrient Document Editor for SharePoint is installed and configured within your SharePoint environment.
- You have the necessary permissions to access and edit documents in the desired SharePoint libraries.
Getting started
Opening a PDF
- Go to your SharePoint library.
- Upload a PDF or choose an existing one.
- If you’re using a file handler installation, click Open from the dropdown and choose Open in PDF Editor. Otherwise, if you’re using other installations such as an online extension or web part, click Open from the dropdown and choose Edit in Nutrient Editor.
Editing your PDF
- Use the integrated editing tools directly inside Microsoft Teams and SharePoint.
- All changes are saved within your SharePoint library using its native version control and access permissions.
For detailed instructions on different PDF operations, refer to our Nutrient Document Editor guides.
Full developer setup using SPFx + Nutrient Web SDK
This option is designed for developers and IT teams who need advanced customization, integration with external systems, and complete control over the PDF viewing and editing experience.
Key capabilities
Has all the features of the no-code viewer and editor, along with the following capabilities:
- Custom UI/UX integration
- External API integration (for example, for automated workflows)
- Custom watermarking and branding
- Support for multiple frameworks, including:
Prerequisites
- Microsoft 365 tenant(opens in a new tab) setup (free through Microsoft 365 Developer Program(opens in a new tab))
- SharePoint Framework(opens in a new tab) (SPFx)
- GitHub account(opens in a new tab) (for cloning our
pspdfkit-sp-online-webpart(opens in a new tab) repository) - Node.js(opens in a new tab) 16.19.0 version or higher
Getting started
Start by cloning our pspdfkit-sp-online-webpart repository using the following command:
git clone https://github.com/PSPDFKit/pspdfkit-sp-online-webpart.gitFor further instructions, refer to our blog on how to build a Microsoft Teams PDF viewer.
FAQs
How can I customize the Microsoft Teams PDF viewing and editing experience?
To customize Microsoft Teams PDF features such as UI layout, tool visibility, branding, or workflows, use Nutrient Web SDK integration with Teams. It enables you to build a fully tailored PDF viewer as a Teams tab app, with control over buttons, behavior, and API integrations.
Where are PDF files stored when using Nutrient’s PDF tools in Microsoft Teams?
PDFs are stored in your connected SharePoint libraries. Neither the no-code editor nor the SDK solution transfers documents to external servers unless explicitly configured.
How do I integrate third-party APIs (for example, digital signatures) into Microsoft Teams PDF workflows?
Use the SDK-based integration to call external APIs. You can trigger workflows such as digital signing, approvals, or content validation directly from the PDF viewer using JavaScript.
Can I limit or control what PDF tools are available to different users?
Yes. The SDK approach enables you to configure toolbar, disable features, or restrict actions based on user roles or permissions using custom logic in your JavaScript code.
Does version control work with both the no-code and SDK PDF editors in Microsoft Teams?
Yes. Both approaches leverage SharePoint’s built-in version history. All edits — whether from the no-code Document Editor or the SDK-based viewer — are tracked securely and saved within SharePoint.