> For the complete documentation index, see [llms.txt](https://docs.empowergpt.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.empowergpt.ai/settings/system-settings/integration-with-confluence.md).

# Integration with Confluence

{% stepper %}
{% step %}
**Atlassian organization admin’s account details**

1. In a new tab, navigate to the <https://id.atlassian.com/manage-profile/security/api-tokens> & make sure to sign in with Atlassian’s organization admin account.
2. Click on the “Create API token” button, and enter a suitable name such as “EmpowerGPT - \[Company Name]”.
3. After clicking on create, you shall be able to copy the API token. Paste the API token, along with the email address of the signed in organization admin.

<div data-with-frame="true"><figure><img src="https://2192711725-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fc2KRGWrkyRO0iZN5Lyeg%2Fuploads%2FtEGf9UoFOEBHeu8A6OJx%2Fimage.png?alt=media&amp;token=3a1ec18b-9806-490c-9d74-8df2babf1d15" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Create and configure an OAuth 2.0 App in Atlassian Developer**

1. In a new tab, sign in to <https://developer.atlassian.com/>
2. Once signed in, click on the “User Menu” on top right to select the “Developer Console” button from the drop-down.
3. Click on the “Create” button under “My apps” section and select “OAuth 2.0 integration” from the drop-down.

<div data-with-frame="true"><figure><img src="https://2192711725-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fc2KRGWrkyRO0iZN5Lyeg%2Fuploads%2F2y1KyUDFlpeHEmX4HMyI%2Fimage.png?alt=media&amp;token=83290743-19a1-4fb0-92bf-ac27bdbf7611" alt=""><figcaption></figcaption></figure></div>

3. Enter a suitable name for the application such as “EmpowerGPT - \[Company Name]”. Check the box below to agree to Atlassian’s developer terms, and click on “Create”.
4. You will land to the application’s “Overview” page after the application is successfully created. Navigate to the “Authorization” page, and click on the “Add” button against “OAuth 2.0 (3LO)” to enable user authorization from Atlassian.

<div data-with-frame="true"><figure><img src="https://2192711725-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fc2KRGWrkyRO0iZN5Lyeg%2Fuploads%2Fmdb01rDz733iQ8W2KF4l%2Fimage.png?alt=media&amp;token=5fd5f09c-0cec-4981-9df1-11473d5df59f" alt=""><figcaption></figcaption></figure></div>

5. Paste the Callback URL provided in the “Callback URL” field and click on “Save changes”.
6. Now navigate to the “Distribution” page and click on “Edit” in front of the “Distribution controls” section. Change the distribution status to “Sharing”.
7. Add your company name as the vendor name and paste the Privacy Policy link under the privacy policy field.
8. Select “No” against the “does your app store personal data?” drop down and click on save changes button at the end.

<div data-with-frame="true"><figure><img src="https://2192711725-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fc2KRGWrkyRO0iZN5Lyeg%2Fuploads%2FWJgWJ568bF9H8Hseq7jE%2Fimage.png?alt=media&amp;token=6031b944-9696-442c-a529-3a11384bd283" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
**Enter details against the created application**

1. Navigate to the “Settings” page.

<div data-with-frame="true"><figure><img src="https://2192711725-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fc2KRGWrkyRO0iZN5Lyeg%2Fuploads%2FKdVMUXQItDMRkriABoHZ%2Fimage.png?alt=media&amp;token=539b9ec5-0c52-4b21-9350-7ac99641b9f5" alt=""><figcaption></figcaption></figure></div>

2. Copy the “Client ID” and “Secret ID” and enter each in the respective field
   {% endstep %}

{% step %}
**Add required permissions to the created application’s API scope**

1. Navigate to the “Permissions” page and click on the “Add” button against the “Confluence API” row. ”Add” button should update to “Configure”.
2. Click on the “Configure” button, and click on “Edit Scopes” under the “Classic scopes” tab

<div data-with-frame="true"><figure><img src="https://2192711725-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fc2KRGWrkyRO0iZN5Lyeg%2Fuploads%2F2DlwTN1TiTPqeYbgobti%2Fimage.png?alt=media&amp;token=4f25b98f-22e3-44be-ba7f-6a9e3ecac273" alt=""><figcaption></figcaption></figure></div>

3. Select the following permissions by check the box under the “Select” column.
   1. Read Confluence space summary
   2. Read Confluence content summary
   3. Read Confluence detailed content
      {% endstep %}
      {% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.empowergpt.ai/settings/system-settings/integration-with-confluence.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.