# Confluence

![confluence-logo-gradient-blue-attribution_rgb.svg](https://assets.relyanceuat.xyz/images/docs/18372422139021/18372436532237.svg)
Atlassian Confluence is a collaborative content management tool enabling teams to create, share, and organize documents, templates, and media in a unified workspace. It facilitates real-time collaboration and integrates with other tools, making it an efficient platform for knowledge sharing and project management.

In order to integrate Confluence with Relyance AI you will need follow an OAuth2 flow and grant permission.

#### In the Relyance AI application:

1. Login to your Relyance account.
2. Navigate to the **Settings** Menu in the bottom left-hand side.
3. Select **Integrations**.
4. Click on the **Vendor Integration** tab.
5. Find the **Confluence by Atlassian** integration card and click it to open its connections.
6. Under **Authentication Method**, choose **Oauth2 / App Token**.
8. Click **Authenticate**.
9. This will bring up Confluence to allow Relyance permissions to connect. Click **Accept**.

![Confluence-3.png](https://assets.relyanceuat.xyz/images/docs/18372422139021/18372428537997.png)

![Confluence-1.png](https://assets.relyanceuat.xyz/images/docs/18372422139021/18372391712141.png)

10. At this point, you should see the following result on the **Vendor** integrations page:

![Confluence-2.png](https://assets.relyanceuat.xyz/images/docs/18372422139021/18372436543245.png)

11. Congratulations, you are now connected to **Confluence**.

<!-- failure-modes:begin (generated from the integration catalog; do not hand-edit) -->

## If the connection reports Connected but returns nothing

These are the ways this integration comes back empty without reporting an error. Generated from the integration catalog, so it tracks what the connection actually asks for.

1. **Authorised, then empty.** The connection carries an authorisation, not a password: it stops returning data if the account that granted it loses access, its own permissions narrow, or the grant is revoked at the vendor. None of that reports an error here -- the connection keeps its last status until the next scan.
2. **A credential rotated at the vendor is not picked up here.** **Workspace ID**, **User Email** and **API Token** are stored when you save the connection, so regenerating the value at the vendor breaks the next scan until it is re-pasted here. Recording the expiry on the connection means Relyance warns you before it lapses.

<!-- failure-modes:end -->

<!-- auth-methods:begin (generated from the integration catalog; do not hand-edit) -->

## Authentication methods and fields

Pick one of these under **Authentication Method** on the connection wizard's **Authentication** step. This table is generated from the integration catalog, so it always matches what the form actually asks for.

| Method | Required | Optional |
| --- | --- | --- |
| **Oauth2 / App Token** | — | — |
| **Custom** | `Workspace ID` (secret), `User Email` (secret), `API Token` (secret) | — |

<!-- auth-methods:end -->

<!-- terraform-examples:begin (generated from the integration catalog; do not hand-edit) -->

## Manage this integration with Terraform

Connections for this integration can be managed as code with the [Relyance Terraform provider](https://registry.terraform.io/providers/Relyance/relyance/latest). Non-secret fields go in `auth.params`; secret fields go in `auth.secrets_wo`, which is write-only — never stored in Terraform state. Rotate secrets by bumping `auth.secrets_wo_version`.

### OAuth (browser authorization)

The **OAuth (browser authorization)** method uses a browser authorization flow, so the connection is created in the Relyance app. Manage it in Terraform afterwards by importing it (`terraform import relyance_integration_connection.example atlassian_confluence/<connection_id>`) or reading it with the `relyance_integration_connection` data source.

### API token

```hcl
resource "relyance_integration_connection" "atlassian_confluence_1" {
  vendor = "atlassian_confluence"
  name   = "<your connection name>"

  auth = {
    method = "api-token"
    params = {
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      workspace_id = var.atlassian_confluence_workspace_id
      user_email = var.atlassian_confluence_user_email
      api_token = var.atlassian_confluence_api_token
    }
    secrets_wo_version = 1
  }

  scans = { "data-inspection" = { enabled = true } }
}
```

<!-- terraform-examples:end -->