Fellow uses the OAuth2 protocol to connect to the Confluence API on behalf of users. OAuth2 ensures that Fellow can only access the specific resources it's been authorized for - these are called scopes. The sections below describe each scope and why it's needed.

Fellow's Confluence integration uses three scopes, all of which are delegated (user-level) permissions.

write:page:confluence

Description: Create and update pages in Confluence.

Why Fellow needs it: Required to export Fellow meeting notes as pages in Confluence. This scope is only used while the user is active in the app.

search:confluence

Description: Search Confluence pages and spaces.

Why Fellow needs it: Required so users can search for and select which parent page or space to export their meeting notes to. This scope is only used while the user is active in the app.

offline_access

Description: Maintain a persistent connection to a user's Confluence account via refresh tokens.

Why Fellow needs it: Allows Fellow to keep the Confluence integration active without requiring users to re-authenticate each time they export notes.