> ## Documentation Index
> Fetch the complete documentation index at: https://docs.voltai.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Confluence

> Create or extend an Atlassian OAuth 2.0 (3LO) integration so Voltai can search Confluence content.

**You'll create:** an Atlassian OAuth 2.0 (3LO) integration — either a new one, or the **same** integration you made for [Jira](/connectors/jira) with the Confluence scopes added.

**We'll be able to read:** page content and space summaries the connecting user can already see in Confluence.

## Steps

<Steps>
  <Step title="Open or create the integration">
    Go to [developer.atlassian.com/console/myapps](https://developer.atlassian.com/console/myapps/) and either open your existing app or click **Create → OAuth 2.0 integration**.
  </Step>

  <Step title="Add Confluence API scopes">
    Open **Permissions** and click **Add** on **Confluence API**.

    Click **Configure** next to Confluence API and grant:

    * `search:confluence`
    * `read:confluence-content.summary`
    * `read:confluence-content.all`
    * `read:confluence-space.summary`

    Atlassian adds `offline_access` automatically.
  </Step>

  <Step title="Set the callback URL">
    Open **Authorization → OAuth 2.0 (3LO) → Configure** and set **Callback URL** to the [redirect URI](/connectors/introduction#redirect-uri-used-by-every-connector).

    Skip this step if you already set it for Jira on the same app.
  </Step>

  <Step title="Copy the credentials">
    Open **Settings** and scroll to **Authentication details**.
  </Step>
</Steps>

## Send us

| Value           | Where to find it                  |
| --------------- | --------------------------------- |
| `client_id`     | Settings → Authentication details |
| `client_secret` | Settings → Authentication details |

## Things to know

<Warning>
  Your Atlassian site must actually have Confluence enabled. Go to **Atlassian Admin → Products** and confirm Confluence is on the same site the user will pick. If the site only has Jira, users will see "Access denied — this app requires access to a Confluence site".
</Warning>

* If you reuse the Jira app, both connectors live on one Atlassian integration and share its scope list. Adding or removing scopes for one affects the other.
* Adding scopes later requires each user to disconnect and reconnect.