> For the complete documentation index, see [llms.txt](https://docs.getdot.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getdot.ai/integrations/knowledge-bases.md).

# Knowledge Bases

Most of what a data team needs to answer a question well isn't in the warehouse — it's the tribal knowledge written down in a wiki, a notes app, or a ticket. Knowledge-base connectors let Dot reach that content directly: its agents can **search**, **read**, and **ask questions** across your documentation, and for some tools **create or update** pages and issues on your behalf.

These are the connectors that answer the original ask behind this whole category — *"all our company documentation lives in Slite / Confluence / Notion, how do I feed that to Dot?"*

## Available connectors

| Connector                                                     | Good for                | Dot can…                                                                                          |
| ------------------------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------- |
| [Slite](/integrations/knowledge-bases/slite.md)               | Slite workspaces        | Ask (hosted Q\&A), search, read notes — **read-only**                                             |
| [Notion](/integrations/knowledge-bases/notion.md)             | Notion workspaces       | Search, read pages & databases, create/update pages, comments                                     |
| [Confluence](/integrations/knowledge-bases/confluence.md)     | Atlassian Cloud wikis   | Search, read, create/update pages, attachments, comments                                          |
| [Jira](/integrations/knowledge-bases/jira.md)                 | Atlassian Cloud issues  | Search, read, create/update/transition issues, comments                                           |
| [Google Drive](/integrations/knowledge-bases/google-drive.md) | Google Workspace Drives | Search and read Docs, Sheets, Slides, PDFs — **read-only**, scoped per shared drive (or per user) |

## How they work

**1. Connect once, in Settings.** Each connector is a card under **Settings → Connections**, in the group the app labels **Context Connectors**. You supply an API token — or authorize via OAuth for Notion, or a service account for Google Drive — and Dot validates it.

**2. Govern each action, in Model → Skills.** Once connected, the connector appears as a **skill** under **Model → Skills**. Expand **Configure permissions** to see each action as its own toggle — an admin turns individual actions on or off. A disabled action is refused with a message naming the exact permission to flip, so nothing runs that you haven't allowed.

**3. Dot uses it at query time.** Unlike a database sync, these connectors don't copy your content into Dot. Dot's agents reach into the source *when a question needs it* — searching, reading, or asking against the live workspace. This keeps answers current and means access always reflects live permissions in the source tool — those of the connected account, or for [Google Drive](/integrations/knowledge-bases/google-drive.md), of whichever drive that connection was scoped to.

{% hint style="info" %}
**Permission defaults follow a simple rule.** Non-destructive reads (and, for Notion/Confluence/Jira, ordinary writes) default **on** — connecting the tool implies you want Dot to use it. Destructive or privacy-sensitive actions (delete, archive, listing workspace members) default **off** and must be turned on explicitly.
{% endhint %}

## Related

Knowledge-base connectors are one of the tools available to [Root, Dot's Context Agent](/train-dot/context-agent.md) — the agent that builds and maintains your organization's knowledge base. Pointing Root at your Confluence space or Slite workspace lets it extract business logic straight from your existing documentation.