Managing GitHub App permissions and organisation access
GitHub Links for Confluence connects via a GitHub App. This page explains how to verify which permissions and organisations the app has access to, and how to grant additional permissions for optional features.
Check which organisations the app can access
Go to your GitHub profile → Settings.
Navigate to Integrations → Applications.
Click the Installed GitHub Apps tab.
Locate Links for Confluence and click Configure.
Under Repository access, confirm the correct organisation and repositories are listed.

If you connected via a Personal Access Token (legacy method) rather than a GitHub App, go to Integrations → Applications → Authorized OAuth Apps and locate Links for Atlassian Confluence to verify org access there instead.
Grant access to an additional organisation
If the app was installed on your personal account but you also need it to access an organisation's repositories:
Open the app's configuration page (as above).
Under Repository access, update the selection to include the required organisation repositories.
Click Save.
Alternatively, a Confluence administrator can disconnect and reconnect via Confluence Administration → Apps → GitHub to re-initiate the connection for a different organisation.
Grant additional permissions for optional features
Some entity types require permissions beyond the defaults:
Feature | Required permission |
|---|---|
Discussions - Read | |
Code scanning alerts - Read | |
Repository security advisories - Read |
To grant these:
Go to your GitHub organisation settings → Integrations → GitHub Apps.
Locate Links for Confluence and click Configure.
Scroll to Permissions and update the relevant permission to Read.
Click Save. GitHub will notify organisation members to re-approve the updated permissions.
Once approved, the corresponding entity types will display correctly in the macro.
Updated: