New Webhook Contributor Role #199440
Replies: 1 comment
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Product Feedback
💬 Feature/Topic Area
Webhooks
Body
Problem:
Currently, all API endpoints relating to webhooks at an organization level require the user to be an organization admin. This means you must be an organization level admin even to query webhook deliveries for a specific webhook.
Solution:
Create a new role, something like 'Organisation Webhook Contributor', which some of these permissions - particularly listing deliveries, or triggering redeliveries. This role wouldn't have permission to update, create or delete organisation webhooks, but could observe deliveries and redeliveries for the selected endpoints. The usecase would be where a non-admin needs to manage webhook deliveries/redeliveries.
Happy to understand why this isn't possible if that's the case as well!
Source: https://docs.github.com/en/rest/orgs/webhooks?apiVersion=2026-03-10#list-deliveries-for-an-organization-webhook
Beta Was this translation helpful? Give feedback.
All reactions