Platform Integrations
Connect Sleeve with Confluence, Notion, GitBook, and other platforms
Platform Integrations
Sleeve integrates with popular documentation platforms to bring all your knowledge into one searchable interface.
Available Integrations
Confluence
Enterprise wiki integration with service account support
Notion
Personal workspace integration via personal tokens
GitBook
Documentation platform integration via personal tokens
GitHub
Repository and static site synchronization
Confluence Integration
Confluence integration supports both organization-wide syncing and individual user access.
Authentication Requirements
Setup Process
Decide between service account (organization-wide) or personal tokens (individual access)
For service account: Create a service account in Confluence admin settings For personal: Generate a personal API token in your Confluence account
- Go to Settings → Integrations
- Click "Add Integration" → Confluence
- Enter your Confluence URL and API token
- Select spaces to sync
Click "Sync" to bring over your Confluence content. Updates are manual for now.
Notion Integration
Notion integration uses personal tokens for workspace access.
Authentication Requirements
- Personal integration token from Notion
- Access to specific workspaces based on user permissions
- Read-only sync from Notion to Sleeve
- No service account available (personal tokens only)
Notion doesn't support service accounts, so each user must authenticate with their own token to access their permitted workspaces.
Setup Process
- Go to Notion → Settings & Members → Connections
- Click "New integration"
- Give it a name and select workspace
- Copy the integration token
- Open each page you want to sync
- Click "Share" → "Add people"
- Add your integration
- Grant appropriate permissions
- Go to Settings → Integrations
- Click "Add Integration" → Notion
- Enter your integration token
- Select pages to sync
GitBook Integration
GitBook integration uses personal tokens for space access.
Authentication Requirements
- Personal API token from GitBook
- Access to specific spaces based on user permissions
- Read-only sync from GitBook to Sleeve
- No service account available (personal tokens only)
GitBook doesn't support service accounts, so each user must authenticate with their own token to access their permitted spaces.
Setup Process
- Go to GitBook → Settings → Integrations
- Click "Create new token"
- Give it a name and select permissions
- Copy the generated token
- Go to Settings → Integrations
- Click "Add Integration" → GitBook
- Enter your API token
- Select spaces to sync
Click "Sync" to bring over your GitBook content. Updates are manual for now.
Sync Behavior
Sync Capabilities by Platform
Future Enhancements
- Automatic syncing with configurable intervals
- Bidirectional sync for supported platforms
- Real-time updates when content changes
- Conflict resolution for concurrent edits
Best Practices
Content Organization
Decide which content to sync based on:
- User access permissions
- Content relevance to your team
- Update frequency
- Search discoverability needs
Use Sleeve's team and space structure to organize synced content:
- Create teams for different platforms
- Use spaces for logical groupings
- Set appropriate visibility (public/private)
Keep original platform content updated:
- Sync regularly to pull latest changes
- Use Sleeve for new content creation
- Maintain platform-specific workflows
Access Control
Synced content inherits the access permissions of the original platform. Users without access to certain spaces/pages won't see that content in Sleeve search results.
Troubleshooting
Common Issues
Getting Started
Ready to connect your existing documentation platforms? Start with our Quick Start Guide to set up your workspace, then return here to configure your integrations.
Platform integrations are designed to bring your existing content into Sleeve for unified search and discovery. For collaborative editing and two-way sync, use GitHub integration.