Data Sources

Data Sources

Super connects to the tools your team already uses — Slack, Linear, Notion, GitHub, Google Drive, and more — so you can search and take action across your company's knowledge in one place.
This guide covers how sources work, how access is controlled, and how to manage connected tools. For setup steps on a specific source, click through from the list below.

How data sources work

Every data source in Super has two properties that shape how your team uses it: a setup method (how it connects) and an access model (who can query it once connected).

Setup methods

OAuth
Click connect, sign in to the source, grant Super access. No admin configuration in the source itself.
Requires configuration in the source
Before Super can connect, an admin needs to set something up inside the source first — typically installing an app, creating a service account, or configuring a delegation. The guide for each source walks through exactly what's needed.
No auth required
Content is either uploaded directly into Super or is publicly accessible, so no external authentication is needed.

Access models

Shared
All workspace members can query the source. No account in the connected tool is required. Workspace admins can further restrict access per connection — see Controlling access to shared sources below.
Mirrored
Super matches each member to their account in the connected tool by email. Members can only query content they already have access to in that tool. No matching email account = no results from that source.
The access model is set by the source type and can't be changed. You'll see it as a badge on each connection in the Data Sources panel.

Supported sources

Click any source for setup steps and details on what's synced.
Tool
What we sync
Setup
Access
Tasks, comments, and metadata from selected projects
Records from selected objects and lists
Table descriptions from connected projects
Pages (no attachments or comments)
Custom data indexed via the public API
.pdf, .pptx, .docx, .html, .txt
All .md files in connected repos
Issues and PRs from public and private repos (no comments or media)
Issues and merge requests from public and private projects (no comments)
Docs, Slides, .docx, .pptx, .pdf (no Sheets, images, or videos)
1,000 most recent deals (max 100 properties each)
Conversations (no articles, contacts, or notes)
Issue descriptions (1 year) and metadata (no comments)
Issues, comments, and metadata from synced teams
Pages under selected roots (no database objects)
Records from connected objects
Pages and OneDrive files (.pdf, .pptx, .docx)
Threads from public and private channels
Your entire documentation
Page content, metadata, and structure
 Zendesk  (beta)
Tickets, including comments and replies, from the past year
 Zoom  (beta)
Meeting transcripts
Attio and Notion combine both access models depending on the content type — see their individual guides for details.

Controlling access to shared sources

For Shared sources, workspace admins can set who in Super can query each connection.
By default, a newly added Shared source is restricted to workspace admins only. To open it up, go to the connection in the Data Sources panel and adjust access:
  • Everyone at {workspace} — set to Can access or Restricted .
  • Specific users or user groups — add them individually and set each to Can access or No access .
Workspace admins always have access, even when a source is restricted.
In the main Data Sources list, the Access column reflects the current setting:
  • Everyone — anyone in the workspace can access this source.
  • Limited — Everyone is restricted, but specific users or groups have been granted access.
  • Admins — Everyone is restricted and no exceptions have been added; only workspace admins can access it.
This section only applies to Shared sources. Mirrored sources follow the original tool's permissions and can't be configured here.

Controlling who can add or manage sources

Admins can decide whether all members or only admins can add, remove, or manage data source connections.
This setting lives under Settings → Security → Create and manage sources.
By default, only admins can manage sources. Only workspace owners and admins can change this setting.

The Data Sources panel

Open the Data Sources panel from the sidebar to view all connections, add new ones, and manage what's syncing.
Every connection is listed individually — so Asana – Dev account and Asana – Marketing appear as separate entries rather than grouped. Click any connection to see its synced root nodes, access badges, and last sync times, or use + New source to add a new connection.

About sync timestamps

A "Last synced" timestamp like 17 hours ago doesn't mean Super has been idle. It means nothing new changed in the source during that window, so there was nothing to update. Super keeps checking in the background, and the timestamp only updates when new content is actually indexed.

Data Handling and Privacy

What gets indexed
Super securely indexes the content needed for search and AI responses. What's indexed depends on each source's capabilities and permissions.
AI and privacy
Only the snippets relevant to a query are sent to the model. The model doesn't retain or train on your data.
Removing data
Disconnecting a source permanently deletes all its indexed content from Super.
Security and compliance
All data is encrypted, stored in the EU, and handled to SOC 2 Type II standards. See the  Security Policy  and  Privacy Policy  for details.

Rate limits

Every tool Super connects to has its own API rate limits. Super manages these automatically — slowing or pausing sync when limits are hit, retrying once they reset, and resuming as soon as more requests are allowed. Previously indexed content stays searchable throughout.
Most of the time you won't notice. For very large sources or historical imports, you may see slower initial syncs or short delays in very recent content. No action required — Super catches up automatically.