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

# Confluence Integration

> Connect a Confluence Cloud site to Corelayer with organization-managed service-account OAuth credentials.

Connect your team's Confluence Cloud site with an Atlassian service account. The connection uses a client ID and client secret managed by your organization, so it does not depend on an employee's personal API token or email address.

## Prerequisites

* A Confluence Cloud site, such as `https://your-team.atlassian.net`
* An Atlassian organization administrator who can manage service accounts
* A service account with Confluence access and permission to view the intended spaces
* Permission to manage integrations in the selected Corelayer group

## Create the OAuth Credentials

In [Atlassian Administration](https://admin.atlassian.com), select your organization and open **Directory → Service accounts**. Select your service account, choose **Create credentials → OAuth 2.0**, and grant `read:space:confluence`. Save the generated client ID and client secret in your password manager.

See [Atlassian's service-account OAuth guide](https://support.atlassian.com/user-management/docs/create-oauth-2-0-credential-for-service-accounts/) for account requirements and credential creation. OAuth scopes do not grant access to spaces the service account cannot already view.

## Connect Confluence

1. Select the Corelayer group that should own the connection.
2. Open **Integrations**, click **Add Integration**, and select **Confluence**.
3. Enter the **Site URL**, **Client ID**, and **Client secret**.
4. Click **Verify and connect**.

Corelayer verifies access to the site's spaces API before saving the connection. Connect another integration to use a different site.

## What the Connection Does

This integration currently connects the site and manages its credentials. Connecting or testing it does not import pages, index documentation, or add Confluence content to investigations.

## Manage the Connection

Open the Confluence integration's **Settings** tab.

* **Test connection:** Open the three-dot menu and select **Test connection** to verify the saved credentials.
* **Rotate credentials:** Create a new OAuth credential in Atlassian, then select **Edit credentials** from the three-dot menu. Enter the new client ID and secret and save. Verify the replacement before revoking the previous credential in Atlassian.
* **Change sites:** Add a separate Confluence integration; the site cannot be changed in the credential edit dialog.
* **Disconnect:** Click **Disconnect** and confirm. Revoke the credential in Atlassian separately if it is no longer needed.

If another administrator updates the connection while you edit, reload the connection and review your preserved draft before saving again.

## BYOC Deployments

The same connection flow is supported for customer runtimes on AWS and GCP. Your deployment needs the Atlassian credential-storage permissions and outbound HTTPS access to `auth.atlassian.com`, `api.atlassian.com`, and your site's `*.atlassian.net` hostname. Ask your deployment administrator or [Corelayer support](mailto:support@corelayer.com) to check the runtime configuration if setup is unavailable.

## Troubleshooting

* **Verification fails:** Check the site URL, credential validity, `read:space:confluence` scope, and the service account's Confluence and space access.
* **Reconnect required:** Use **Edit credentials** to supply service-account OAuth credentials.
* **Settings cannot be changed:** Ask someone with integration-management permissions in the selected Corelayer group to make the update.

To connect Jira as well, follow the [Jira integration guide](/integrations/jira.md).


## Related topics

- [October 2026](/changelog/october-2026.md)
- [Jira Integration](/integrations/jira.md)
- [Linear Integration](/integrations/linear.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.