Keep your team on the latest content by syncing files directly from the tools where that content already lives. Content Syncing connects Google Drive, SharePoint, or Confluence to Spekit, so the resources your team relies on stay current in Spekit without manual re-uploads.
This article covers what syncing is, what you can sync, who can do it, and how synced content behaves. For step by step setup, see the article for your source.
Governance note: Syncing content into Team Hub Topics requires Account Admin, Team Admin, or Expert access in Spekit. This restriction does not apply to Deal Rooms, where users can sync files directly within their own Deal Rooms.
📌 Quick-Jump Topics
1. What Content Syncing does
Content Syncing connects a source system to Spekit so you can bring specific files in and keep them current automatically. Instead of downloading a deck, uploading it to Spekit, and repeating that every time it changes, you sync the file once and Spekit refreshes it for you.
Synced content is more than stored, it is surfaced. Files you sync are searchable in Spekit and served up by the Spekit AI Sidekick in the flow of work, so your team can find the right deck, template, or answer without switching tools.
What you get:
| Benefit | What it means for your team |
|---|---|
| Always current | Spekit refreshes synced files from the source automatically, so reps always see the latest version. |
| Centralized and findable | The right materials live in one place and surface through search and AI Sidekick, not across scattered drives. |
| Less manual work | Update the file once in the source. No re-uploading to keep Spekit current. |
2. What you can sync
You can sync from three sources. What you can bring in depends on the source, so the supported file types are not identical across all three.
| Source | Supported content |
|---|---|
| Google Drive | Google Docs, Sheets, and Slides, plus PDF, PPTX, DOCX, and XLSX |
| SharePoint | PDF, PPTX, DOCX, and XLSX, plus published SharePoint Pages |
| Confluence (Beta) | Pages |
Syncing is always selective. Your entire drive or site does not come across. You choose the specific files or folders to sync, and only what you sync appears in Spekit.
3. Who can sync content
Access depends on where the content is going: shared Team Hub Topics, or a user's own Deal Room.
| You want to sync into | Who can do it |
|---|---|
| Team Hub Topics | Account Admins, Team Admins, and Experts |
| A Deal Room | Any user with access to that Deal Room, within their own Deal Rooms |
Each Admin or Expert connects their own source account. Connecting your account does not let other Admins or Experts import from it, so more than one person can keep the connection healthy.
4. How synced content behaves
Once a file is synced, a few consistent rules apply no matter which source it came from.
| Behavior | What happens |
|---|---|
| Automatic updates | Spekit refreshes synced files from the source within a few hours. Use Force Sync on a file to push an update sooner. |
| Easy to identify | Synced files show a source icon and a Go to Source button that opens the original. |
| Permission-aware | A user can access synced content in Spekit, but cannot open the original file unless they also have permission in the source system. |
| Source file deleted | The file drops out of Spekit after the next sync. |
| Source file moved | The file stays available and the Go to Source button updates automatically. |
| Account disconnected | Content already imported stays in Spekit, but future changes stop syncing. Other connected accounts keep working. |
5. Best practices for syncing
These habits apply no matter which source you sync from. The source articles add a few tips specific to Google Drive, SharePoint, and Confluence, but start here.
| Best practice | Why it matters |
|---|---|
| Decide who owns what | Assign synced content to the right Topics and Experts so owners know what they maintain. For example, Marketing owns the "Customer Stories" Topic while Enablement owns "Sales Plays." Spekit auto-detects duplicate files, but agreeing on ownership up front gets you ahead of duplicate effort. |
| Sync living content, upload static content | Sync files that change over time, like decks, pricing, and playbooks, so reps always have the current version. Upload one-off, moment-in-time documents such as QBR recaps or signed contracts instead. |
| Set the right permissions before you share | Confirm the intended audience can view the file in the source system. For external sharing, make the content link-viewable in the source and turn on External Sharing in Spekit, so buyers do not hit an access wall. Test by opening the Spekit link in an incognito window: if you can view it there, so can your buyer. |
| Keep the connection healthy | Have more than one Admin or Expert connected per source, so syncing continues if one person disconnects or leaves. |
| Measure impact with the Buyer Engagement Dashboard | See which synced content reps actually use and share, then prioritize updates on the high-value pieces and retire what no one opens. Syncing content is step one, knowing it is used is step two. |
| Spot-check core files monthly | Assign one Admin or Expert to check core files, like the current pitch deck and pricing sheet, once a month to confirm they are still syncing and current. A five-minute check beats a rep sending a buyer last quarter's pricing. |
6. Where to go next
Pick the article that matches what you are doing:
- Set up a source and sync files: see the overview for Google Drive, SharePoint, or Confluence.
- Common questions: see the Content Syncing FAQs.
- Data privacy and security: see the Content Syncing Data Privacy and Security FAQs.
- Something not working: see Troubleshooting Content Syncing.