GitHub Integration: Alternative Permission Scope

[Danilo Spinelli]

For the integration between Atlassian Compass and GitHub (specifically for collecting event-based metrics and creating new repositories), the GitHub app currently requests ‘administration’ permissions across the entire GitHub organization.

We would like to know if there is an alternative approach (e.g., using a personal access token) that allows permissions for creating new repositories without granting broader administrative rights, such as the ability to modify or delete existing repositories.

This requirement arises from our organization's policy, which enforces strict segregation of repository permissions.

Thank you for your support!

[Tomislav Tobijas]

Hi @Danilo Spinelli ,

Have you found any 'solution' for this?

There's a feature request related to GitHub integration and granular permissions (although it's for Jira), but it might be worth taking a look at it and potentially dropping a vote and a comment: JRACLOUD-89994: Ability to bypass write access permission to GitHub Cloud repositories for "GitHub for Jira" app 

What you could also do is to reach out to Atlassian Support and potentially ask them to raise a new feature request (or maybe offer some workaround, as this is, as you say, a security-related topic).

Cheers,
Tobi