Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

GitHub integration permissions


We are looking at connecting the GitHub integration with Compass. We noticed that it wants the following permissions:

* Read access to actions, metadata, and organization events
* Read and write access to code, deployments, organization hooks, pull requests, and repository hooks.

Our SecEng team is looking for a better breakdown of what the possible write actions could be so they could correlate within audit logs.

2 answers

1 vote
Dave Parrish _Atlassian_
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 16, 2022

Hi @Michael Juarez 👋  It's Dave from the Compass product team. The GitHub integration needs write permission in order to create organization webhooks. This is the only write operation that the integration currently performs.

Webhooks are used for listening to several types of events-

  • Push events - for handling changes to compass.yml metadata
  • Pull request events - for calculating PR-related metrics
  • Deployment events - for handling deploy events

Hope this is helpful! Please let me know if you have any further questions.

Why create organization webhooks when you can do it on a per-repo level? The latter would not require org admin permissions, which sounds scary and also comes with internal gatekeeping within the organization.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events