Data Sources
Super connects to tools like Slack, Linear, Notion, GitHub, and Google Drive so you can search and take action across your company’s knowledge in one place.
Use this guide to understand how sources work, how Super handles your data, and how to manage connected tools.
Supported Data Sources
Click any source in the list to view detailed setup steps and information on what Super syncs, how often it refreshes, and what permissions are required.
Permissions vary by source.Some tools support item-level permissions; others do not. Read more below .
Task, comments and some meta from selected projects.
Super only indexes content users can see in Asana.
Index custom data via the public API, bound to a parent object.
Anyone in your Super org can search content from connected custom sources.
Issues and PRs (no comments or media).
Anyone in your Super org can search content from connected public repositories.
Issues and merge requests (no comments).
Anyone in your Super org can search content from connected public projects.
All
.md files in the repository.Anyone in your Super org can search content from connected private or public repos.
Issues, comments, and metadata from synced teams.
Users must have a Linear account with the same email. Private Linear teams stay private.
Pages under selected root (no database objects)
Super indexes connected pages; all Super members get results based on what’s been synced.
Threads from public and private channels
Users are matched by email, so each person can only search and receive answers from channels they are a member of.
Page content, metadata and structure.
Anyone in your Super org can search content from the connected website which must be publicly available.
Attio
full guide coming soon
Records from selects objects and lists.
Confluence
full guide coming soon
Pages only (no attachments or comments).
Files
full guide coming soon
.pdf, .pptx, .docx, .html, and .txt files
Google Drive
full guide coming soon
Docs, Slides, .docx, .pptx, .pdf (no Sheets/images/videos)
Hubspot
full guide coming soon
1,000 most recent deals (max 100 properties each)
Intercom
full guide coming soon
Conversations only (no articles or contacts)
Jira
full guide coming soon
Issue descriptions and metadata (no comments)
SharePoint
full guide coming soon
Pages and OneDrive files (.pdf, .pptx, .docx)
Public Help Center
full guide coming soon
Websites based on GitBook, Intercom, Notion, Slite, Super, and Zendesk are currently supported
Slite
full guide coming soon
Your entire documentation.
Data Handling and Privacy
What happens when you connect a data source
Super securely indexes the content needed for search and AI responses. Exactly what is indexed depends on the source’s capabilities and permissions.
AI usage and privacy
Only the relevant snippets of content are sent to the model when generating answers. The model does not retain, train on, or learn from your data.
Permission enforcement
Super enforces permissions based on what each connected tool makes available through its API.
For many sources, Super can mirror the original access controls, so users only see items they already have permission to view.
For others, the API may not provide item-level permissions. In those cases, Super indexes the content selected during setup and makes it available to all members of the Super workspace who have access to that source.
Because of these differences, team members may see different content or item counts depending on the tool connected and the permissions it exposes.
Data removal
If you disconnect a source, all indexed content from that source is permanently deleted from Super.
Security and compliance
All data is encrypted, stored in the EU, and handled according to SOC 2 Type II–certified standards.
Controlling Who Can Add or Remove Data Sources
Admins can decide whether all members or only admins can add or remove data sources.
This setting is available in the Data Sources panel or under Settings → Security.
By default, all members can manage sources, but only owners and admins can change this setting. It doesn’t affect who can view or search existing sources.
Adding and Managing Sources
In the Data Sources panel, you can view all sources added by your team and manage them:
- Add new connections
- Remove or refresh existing ones
- Review sync status and content counts
Understanding the Data Source Panel
The Data Sources panel gives you an overview of everything connected to Super, including what’s syncing, who added it, and how fresh the content is.
Sources in Sync
Lists all data sources currently connected and actively syncing.
What you’ll see:
- The source’s name, icon, and sync status
- Expandable items for sources that support nested content (e.g., repositories, folders)
- Bulk actions for syncing or removing multiple sources
Notes:
- Only active connections appear here
- You may see different sources from your teammates depending on permissions inside the original tool
Connected by
Indicates who originally connected the source or specific item to Super.
Notes:
- This person does not control access for others
- Access always follows your permissions in the original tool
Content
Displays how many items from that source you can search in Super (documents, issues, tasks, messages, etc.).
What you’ll see:
- A count such as “150 items”
- Sometimes a fraction such as “50/100 items,” showing what you can access versus the total available in the source
Notes:
- Large sources index gradually
- Some sources sync continuously, others every 6–12 hours
- The number always reflects what is currently searchable in Super
Last Update
Shows the most recent time Super received new content from this source.
Key clarification:
A timestamp like “17 hours ago” does not mean Super has not synced for 17 hours. It means nothing new changed in the source during that period, so there was nothing to update. Super continues checking in the background even when the timestamp stays the same.
Statuses:
- “2 hours ago” → new content was recently indexed
- “Syncing” → a sync is currently in progress
- “Error” → Super could not complete the sync (hover for details)
Notes:
- Sync frequency varies by source
- Initial syncing for large sources may take longer
- A source may show no updates simply because no new content was added in the original tool
Rate Limits in Super
Super connects to a variety of tools, each with its own API “rate limits” that control how many requests an app can make within a certain timeframe. Super automatically adapts to these limits so your connections remain stable.
Why rate limits exist
Tools like Slack, Linear, Jira, and GitHub enforce rate limits to ensure consistent performance and prevent overload. For example, a tool may restrict how many issues can be fetched per hour or how frequently message history can be requested.
How Super handles rate limits
Super manages rate limits entirely behind the scenes. When a limit is close or reached, Super will automatically:
- Slow down or pause syncing
- Retry once the external tool resets its limit
- Resume indexing new content as soon as more requests are allowed
- Keep all previously indexed content searchable
What this means for you
Most of the time, you will not notice rate limiting at all. In rare cases, typically when connecting a very large source or syncing historical data, you may see:
- Slower initial imports
- Delayed updates
- Temporary gaps in very recent content
Once the limit resets, Super automatically catches up.
No action required
Rate limiting does not require you to reconnect or adjust anything. Super handles recovery automatically as soon as the external tool allows more requests.