You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Greetings,
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.
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-
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.