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

# Confluence pages

> Bring Confluence pages into Knowledge and what agents recall, each with a link to the page, and each person sees only the pages Confluence lets them open

Connect Confluence and choose the spaces you want. Their pages show in
**Knowledge** and in what agents recall, each with a link back to the page in
Confluence. Pages are usually edited in Confluence, and the next sync brings
the change over. An edit you make to a page in Knowledge can also be written
back, with your approval (see **Write an edit back** below).

## Each person sees only the pages they can open

Whenever someone reads Confluence pages through Orchestra (Knowledge, recall,
an agent's context), Orchestra asks Confluence, **as that person**, which of
the pages they may open, and shows only those. Nothing about who can see what
is stored. If Confluence cannot be asked (the person has not linked their
login, their login expired, or Confluence does not answer), they see no
Confluence pages rather than too many.

## Connect (Orchestra's cloud)

1. **A workspace admin connects.** On the Confluence card in **Settings,
   Integrations**, choose **Connect Confluence** and approve on Atlassian's
   screen. If your login reaches several Atlassian sites, the card then asks
   which one to sync.
2. **The admin chooses the spaces.** The card lists the spaces the connection
   can see; pick the ones to sync.
3. **Each person links their own login.** On the same card, **Link my login**
   approves Atlassian once for yourself. That is the login Confluence is asked
   as when you read pages. Without it you see no Confluence pages.

## Connect (Orchestra Local)

On a laptop, Confluence connects with your own Atlassian account, and every
page read asks Confluence whether you can still open it.

**Sign in with Atlassian (recommended).** Choose **Sign in with Atlassian** on
the Confluence card in the desktop app's **Settings, Integrations**, or run:

```sh theme={null}
orchestra integrations connect confluence
orchestra integrations confluence spaces
orchestra integrations confluence configure ENG DOCS
```

Atlassian requires the app's secret to finish a sign-in and to renew it, so
Orchestra's API does those steps for your laptop: the sign-in is sealed so only
your laptop can open it, and Orchestra keeps none of it. Pages come straight
from Confluence to your laptop.

**Or use an API token.** Create one at
[id.atlassian.com, Security, API tokens](https://id.atlassian.com/manage-profile/security/api-tokens),
then fill in the token form on the card, or run:

```sh theme={null}
orchestra integrations connect confluence --site your-company.atlassian.net --email you@company.com
```

The token is read with your typing hidden, kept in your laptop's keychain and
sent only to Confluence. See [Local and cloud](https://docs.orchestrahq.ai/integrations-local-and-cloud.md)
for where each integration runs.

## Write an edit back

An edit you make to a Confluence page in Knowledge is saved as a proposal. When
you approve it, Orchestra writes it to the page **as you**, so Confluence shows
you as the author and applies your own edit permission. Three things must be in
place:

1. **Write-back is on** for the workspace (Settings, Integrations, **Write
   issues back to trackers**). It is off until an admin turns it on.
2. **You allowed writing pages.** On Orchestra's cloud: on the Confluence card,
   after linking your login, choose **Allow writing pages** and approve on
   Atlassian's screen. On Orchestra Local, see below.
3. **The page can take the edit.** Knowledge holds a page as text, without its
   macros, images, attachments, mentions or links to other pages. Orchestra
   never writes over a page that has any of those, because the edit would
   erase them; it tells you what the page holds, and you make that edit in
   Confluence. It also refuses an edit made on an older version of the page.

Until all three hold, an approved proposal stays saved and waits, and the
message says what is missing. Orchestra never creates or deletes a page.

**On Orchestra Local**, the edit is written as the laptop's owner, with the
login this laptop holds. An API token already carries your own Confluence
rights. Signing in to Atlassian asks to read and write pages in one consent; if
you signed in before writing was possible, sign in again (Settings,
Integrations, or `orchestra integrations connect confluence`) to allow it.

## How fresh it stays

Orchestra asks Confluence for changes every few minutes. A page deleted,
archived or moved out of a synced space leaves Knowledge and recall on the
next pass. **Sync now** on the card pulls right away.

## What syncs

| | |
| - | - |
| **Content** | Title and text, as Markdown, with the page's place in its tree |
| **Where** | The space, and a link to the page |
| **Who** | Who last edited it in Confluence |
| **Removed** | Deleted, archived and moved-out pages leave Knowledge and recall |

## When an Atlassian account is closed

Orchestra reports the Atlassian accounts it holds (page authors, and the account
that connected) to Atlassian every week, as Atlassian requires. When Atlassian
says an account was closed, Orchestra removes that person's name and email
within a day and keeps the pages themselves.

## Disconnect

On the card, **Disconnect** stops syncing and deletes the workspace's
authorization; synced pages leave Knowledge and recall. **Unlink** removes
only your own login.

On a laptop, `orchestra integrations disconnect confluence` removes the pages
and the sign-in or API token from your keychain.


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