Sync SharePoint files and pages into shared Team Hub Topics so your whole team always has the latest version. This guide is for the people who own team-wide content: Account Admins, Team Admins, and Experts.
ℹ️ Before you start: A SharePoint account must already be connected to Spekit, including the one-time Entra consent. Syncing into Team Hub Topics requires Account Admin, Team Admin, or Expert access. To connect, see Connect SharePoint. Reps sync into their own Deal Rooms instead, see Sync SharePoint Content into Your Deal Room.
1. How to sync files and pages
Choose the specific content to bring into Spekit. Your whole SharePoint environment does not sync, only what you select.
- Open the Spekit Hub (Web App) or the Sidekick (Chrome Extension).
- Click the Team Hub button, then click + Add New.
- Click File Sync. Your connected SharePoint sites appear here.
- Use the navigation or search bar to find the files, folders, and published pages you want.
- Select your content and click Next.
- Assign it to the relevant Spekit Topic(s) so it is organized and easy to find.
- Fill in any Custom Fields to add context.
- If reps will share the content with buyers, toggle external sharing on (for customers with trackable links enabled).
- Click Sync Files to finish.
⚠️ Important: SharePoint sites with "portals" or "app catalog" anywhere in their URL (for example, customer-portals) may not appear in the site picker. This is a known limitation, not a permissions issue. Contact the Spekit support team if a site you expect to see is missing.
💡 Pro Tip: Sync a whole folder rather than picking files one by one when a team owns a stable set of resources. New files added to that folder in SharePoint come into Spekit on the next sync, so you are not back in the picker every week.
2. How SharePoint Pages sync
SharePoint Pages behave a little differently from files, because SharePoint tracks published state and versions. Knowing these rules up front prevents surprises about what does and does not appear.
| Behavior | What to expect |
|---|---|
| Published content only | The file picker shows only content that is published in SharePoint. Drafts and unpublished pages do not appear. |
| Major versions only | Spekit syncs major versions (for example, 3.0). Minor version drafts (for example, 3.1) are ignored during sync. |
| Versioning must be enabled | Enable both minor and major versioning on the site you pull from, or pages may not import. |
| Unpublishing does not remove | Unpublishing a page in SharePoint does not remove it from Spekit. Manually manage or delete the content in Spekit if it should no longer appear. |
💡 Pro Tip: Treat unpublishing in SharePoint and removing in Spekit as two separate steps. If you retire a page in SharePoint, add a quick reminder to delete it in Spekit too, or reps may keep surfacing a page you meant to pull.
3. How to update a synced PDF
If a PDF in Spekit is synced from SharePoint, you can update it without re-syncing by replacing the original file in SharePoint. The key is to keep the original file ID so the link to your Spekit content stays valid.
- Prepare the new PDF. Give the new version the exact same name and file extension as the original (for example,
report.pdf). - Upload it to SharePoint. Go to the document library where the original is stored, then click Upload → Files and select your new file.
- Choose "Replace existing file." When SharePoint sees a file with the same name, choose Replace the existing file rather than keeping both.
- Verify the update. SharePoint keeps the same file ID. Confirm by opening the document using its original link.
Keep in mind:
- Versioning: If your SharePoint library has versioning enabled, you can still restore previous versions of the PDF if needed.
- Link integrity: This preserves the link, so your Spekit content stays valid. Do not rename or move the file in SharePoint after replacing it, or the link will break.
- Content approval: If content approval is enabled in your library, an admin may need to approve the new PDF before it becomes visible.
💡 Pro Tip: Never "delete and re-upload" a synced PDF to update it. That creates a new file ID and breaks the Spekit link. Always use Replace so the same ID carries through and Spekit updates on its own.
4. Best practices
These build on the general syncing best practices in the Content Syncing Overview. The habits below are specific to SharePoint.
| Best practice | Why it matters |
|---|---|
| Sync from a shared Team Site, not a personal folder | Store source files in a shared SharePoint Site rather than a personal folder or OneDrive, so the content stays reliable and maintained even if one person is out or leaves. |
| Protect the SharePoint connection | Make sure your Microsoft 365 admins (usually IT) do not change the enterprise application setting that allows Spekit's access to SharePoint files, or syncing will stop. |
| Update files with Replace, not delete-and-re-upload | Using SharePoint's Replace option keeps the same file ID, so Spekit auto-updates. Uploading a new file with the same name creates a new ID and must be re-synced. See section 3. |
| For Pages, publish and enable versioning | Only published pages sync, and only their major versions. Enable both minor and major versioning on the site, and remember that unpublishing a page in SharePoint does not remove it from Spekit. See section 2. |