Atlassian

Last verified: 31 July 2026

Remly connects to Atlassian products through OAuth, with read-only access. Remly cannot create, edit, transition, or delete anything in Jira or Confluence.

Account ownership

Each connection is owned by the Atlassian account that authorises it, and Remly sees only what that account can see. Connecting with a personal account does not grant Remly access to projects or spaces that account cannot already open.

Jira and Confluence are connected separately, even when they live on the same site. Authorising one does not authorise the other.

Site selection

If your Atlassian account has access to more than one site, you choose which site to connect during setup. To index more than one site, connect the connector again and pick the other site.

Selection fencing

Both connectors ask you to narrow what they cover after choosing a site: projects for Jira, spaces for Confluence. Changing that selection later is protected by a generation fence, so cleanup for a removed project or space is scoped to the selection it belonged to. A sync that fails partway through a selection change cannot delete content you meant to keep.

Credentials

Atlassian issues OAuth tokens with a refresh cycle. Remly stores the access token, refresh token, expiry, and granted scopes as an encrypted bundle and refreshes before expiry. If the grant is revoked or expires, the connector flips to an error state with a Reconnect action, and sync pauses until you reconnect.

Disconnecting

Disconnecting either connector immediately and permanently deletes that connector's sources, documents, text chunks, embeddings, and permissions. Your account and every other connector are unaffected, and nothing in Atlassian itself is touched.

You can also revoke Remly from your Atlassian account settings. If you do, the connector flips to an error state on its next sync attempt.

Plan requirement

Both are cloud connectors and require the Full tier. See Plans and billing.