Search brings your connected sources into one place. An organization admin allows integrations and configures their sources. Teammates then connect their accounts when required. Each person searches with their own access.
Add your first source
Choose an integration
Open Settings → Sources → Add source and choose an integration. Unavailable integrations need deployment configuration before they can be connected.
Connect the content
Follow the integration's Setup guide. Confluence connects a site and selected spaces; Jira adds projects; GitHub adds a repository; GitLab adds a project; Slack configures its app, then channels or DMs. Google service-account setup connects Drive, Gmail, or Calendar with the selected users and filters.
Select Connect & Sync for a central account, or the form’s Add or Set up member accounts action for member accounts. More options contains additional filters. Saving a connection does not invite teammates or authorize their accounts.
Connect and search
For member-account sources, open Integrations in the main sidebar and select Connect for the integration if prompted—even if you created the source. Complete authorization in the new tab. Central Google sources need no personal connection: join with a matching verified Workspace email and open Search to find documents, or Home to ask the assistant about them. Documents become available as background indexing progresses.
Source availability depends on the deployment and organization policy. An unavailable source needs operator configuration before setup can continue. If an existing provider asks for a configuration update after a deployment change, an admin selects More → Update sign-in settings on this page, then affected teammates reconnect.
Choose the right connection method
Sources can use member accounts or a central connection. Gmail, Google Calendar, and Google Drive support Google Workspace service accounts with domain-wide delegation. Confluence supports a central service account with a personal identity connection for each reader. GitHub supports an App installation. GitLab supports a self-managed instance administrator token, or a non-admin token with uploaded CSV permissions.
| Method | What the admin does | What teammates do |
|---|---|---|
| Member accounts | Allows the provider and adjusts shared filters when needed. | Connect their own accounts. Studio lists documents using each member's access. |
| GitHub App installation | Installs the App, selects it under Sync documents with, and adds repository sources. | Connect GitHub once. Studio checks each reader's current repository access before returning installation-indexed content. |
| Google Workspace service account | Configures domain-wide delegation, supplies a Directory administrator email, and selects users and content filters. | Join with a matching verified email. No personal Google connection is needed for that source. Gmail remains private to the mailbox owner; Calendar preserves each person's event view; Drive uses file permissions. |
| Confluence service account | Connects an account that can read the selected content and its permissions. | Join the organization and connect Confluence to establish identity. |
| Administrator token / Non-admin token (GitLab) | Connects one self-managed project. Administrator tokens refresh permissions from GitLab; non-admin tokens use uploaded CSV permissions. | Join with a verified email matching GitLab or the uploaded user mapping. No personal connection is needed. |
Open an integration from the Sources list to manage its connections. Use Connect service account for Google, Add Confluence site, Add projects for Jira, Add repository for GitHub, Add project for GitLab, or Add channels or DMs for Slack.
For personal connections, teammates select Connect beside the integration in the main Integrations page. Existing sources reuse the admin's content selection. If no source exists yet, setup may ask for content after account authorization. Admins can edit connection filters afterward in Settings.
Some member sources offer Sync documents with, either directly in setup or under More options. Connected members uses members' accounts for both content and access checks. Selecting a dedicated account uses it to fetch content; members still connect to establish which documents they may search. For GitHub organization sources, choose Connect GitHub App in this field to connect an installation. Account for browsing only helps an admin pick source options—it does not enroll that account for Search.
An administrator connection does not grant everyone access to everything. Search applies the source's supported permission rules.
Connector guides
| Source | Content | Connection in Search |
|---|---|---|
| Confluence | Pages and blog posts | Service account or member accounts; each teammate connects |
| GitHub | Repository text files | App installation or member indexing; each teammate connects |
| GitLab | Repository files, wikis, issues, merge requests | Self-managed administrator token, or non-admin token with CSV permissions; no member connection |
| Gmail | Email thread text | Delegated service account or member accounts |
| Google Calendar | Meetings | Delegated service account or member accounts |
| Google Drive | Supported Drive files | Delegated service account or member accounts |
| Jira | Issues | Each member's Jira account |
| Slack | Channel messages and threads | Slack app installation plus each member's authorization |
Bring your team
Invite people through the organization's Settings → Members, or use your organization's SSO provisioning. Share the organization's Home or Integrations URL. People need their own Studio account and organization membership; they do not need access to a workspace. Connecting an external account alone does not grant organization membership.
Open Settings → Sources → People to view account contributors and their connection status. Choose an integration in the filter to inspect its connections or send a targeted Request connections invitation. All integrations shows each person's connected providers and accounts needing reconnection.
Connection requests do not grant organization membership. See Connect your account for the teammate walkthrough.
Revoke all account access withdraws every account that person contributed to the organization, including other providers. It does not remove their organization membership.
Manage sources and documents
Open Settings → Sources, choose the integration, then select its site, project, repository, or account connection. Each row identifies its account method and shows its sync status.
Edit Settings to change an existing connection's filters. Adding another connection creates a separate selection. For Gmail, one member-account connection is usually enough: its filters apply separately to each connected mailbox, including accounts connected later. A central Google connection applies to its selected Users, or all active users when that field is blank.
| Connection tab | What you can do |
|---|---|
| Documents | Find indexed documents, inspect processing status, retry failed indexing, or exclude and restore documents. |
| Settings | Edit the source's scope, filters, and supported indexing credentials. Select Save to apply changes or Discard to undo them. |
| Sync history | Review run dates, document changes, and any sync or account errors. |
Sync using shows the method selected when the source was created. Add a new connection to change that method. To replace a supported indexing credential, select its replacement and use Change service account or Change account, as shown.
The connection header offers Sync now, Pause syncing or Resume syncing, and Remove connection. Manual runs have a 60-second cooldown after a successful sync finishes; failed or partial runs can be retried immediately. Pause syncing becomes available when the current sync finishes.
To deactivate an entire integration, open it from Settings → Sources, select Deactivate, and confirm. Its content becomes unavailable in Search, Assistant, and MCP; saved connections remain. Select Activate on that integration to enable it again.
Usage stats
Settings → Sources → Stats shows successful Search invocations, active people, and results returned. Filter by entry point and a preset or custom date range of up to 90 days. Dates use UTC. Source usage counts requests that returned content from each integration; it is not a click or citation count. Tracking starts when enabled and does not backfill earlier activity.
Search, Assistant, and MCP
Search in the organization sidebar finds documents directly. The assistant on Home can search and read the same sources to answer questions with citations. Conversations are private to their author, including when another organization member is an admin.
To use these sources from Claude, Codex, Claude Code, Cursor, or another compatible app, open Settings → Search MCP. Each person signs in with their own Studio account. The server provides search, read_document, and chat; chat starts a new private Studio conversation. See Search MCP for app setup, permissions, and limits.
Check that it works
- Let the first sync finish, then search for a distinctive phrase in a document you can open in the source.
- Open the result's source link and confirm the document is the expected one.
- Ask a teammate with different source access to repeat the search. Documents restricted to you should not appear for them.
- Change or remove a test document's access in the source and check again after the next completed content and permission refresh.
Search runs background syncs on an hourly schedule. Large sources, provider limits, and indexing queues can delay completion. Results are indexed copies, so edits appear after syncing. Permission refresh behavior depends on the connector: GitHub sources indexed through an App installation also check the reader's current repository access before returning indexed content.
If indexing needs attention
A completed sync means the source was checked; some documents may still be indexing. The main Integrations page shows one row per integration with a connection or indexing status. Sources that do not require personal authorization remain searchable without a Connect step. Detailed document counts and errors are available to admins under Settings → Sources.
As an admin, open Settings → Sources, select the integration, then open its connection. In Documents, select Failed from the status dropdown to inspect those files. Use the search field to find a document by name. Select Retry indexing beside a file to try again. Exclude removes a file from search; select Excluded and then Restore to include it again. Fix a disconnected account or source configuration before retrying a sync that needs attention.
Temporary indexing-capacity waits retry automatically in the background. If automatic retries are exhausted, the document appears as failed so an admin can retry it. Other searchable documents remain available while this work finishes.
These guides cover permission-aware Search sources. For a general knowledge base used by workflows, see Knowledge-base connectors; its workspace access settings are a separate choice.