Knowledge sources Private Preview
Connect the wikis and repositories your teams already write in, so Atlan agents can read them and turn them into governed context.
Knowledge sources are the wikis and repositories your teams already write in. Connecting one lets Atlan agents read it and turn what's written there into governed context, such as business terms in your glossary.
Knowledge sources aren't connectors. A connector crawls a system and creates assets in Atlan on a schedule. A knowledge source is read at run time by an agent, creates no assets by itself, and never writes back to the system it reads.
What you can connect
| Source | What agents can read | Availability |
|---|---|---|
| GitHub | Repository READMEs, docs, and markdown files | Available |
| Confluence | Spaces and pages, through Atlassian's Rovo MCP server | Available |
| SharePoint | Document libraries: policies and SOPs | Coming soon |
| Glean | Everything already connected to Glean | Coming soon |
| Google Drive | Docs and Sheets in shared drives | Coming soon |
How access works
An admin connects each source once, in Settings → Integrations. Every agent in the workspace can then select it. Nothing is configured per agent, and no end user is asked to sign in to a source.
Each connection holds a read-only credential that you provide. That credential is the access boundary: an agent can read exactly what the credential can read, and nothing more. Narrow the credential and you narrow every agent that uses it.
A service account gives you space-level or repository-level control, survives someone leaving the company, and can be revoked centrally without touching anyone's own access. A personal token inherits that person's full access and stops working when they change teams.
Connections can't write to your source system. Neither integration requests write scopes.
Connect a source
- In your Atlan workspace, click Settings from the left sidebar.
- Under Team, click Integrations.
- Click the MCP filter to show knowledge sources.
- Find the source you want and click Connect.
- Enter the credentials for that source, then click Connect.
Atlan verifies the credentials before storing them, so a successful connection means the credential works. There is no separate test step.
One connection per source, per workspace. Connecting a second credential for a source replaces the one in use for every agent, so treat credential rotation as an update rather than a new connection.
Rotate or revoke credentials
On a connected source, click Update credentials. Create the new credential first, update it in Atlan, confirm the connection succeeds, and then delete the old one. Deleting a credential at the source stops agent access immediately.
Removing a connection doesn't detach the agents that used it. Those agents keep their configuration, lose their access, and find nothing on their next run. Review the agents that used a source before removing it.
Need help
If you need assistance after reviewing this page, contact Atlan support.
See also
- Connect GitHub: fine-grained token setup
- Connect Confluence: Rovo MCP prerequisites and scopes
- Understand agent templates: what agents do with a knowledge source
- Atlan for AI agents: using Atlan as the governed context layer for your own agents