Allow installers full control of permissions requested by GitHub Apps

[SampsonCrowley]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Apps

Body

GitHub App installations should allow the installing user or organization administrator to reduce any permission requested by the application.
For every requested permission, the installer should be able to select:
write → read → none

The application may warn that reduced permissions can cause features to stop working, but the installer should retain final control.

Effective permissions should be:
app requested ∩ installation approved ∩ user permissions

GitHub already supports restricting an installation to selected repositories and allows an app itself to request reduced permissions when creating installation tokens. The missing security control is allowing the resource owner to enforce that same attenuation.

This matters especially for applications that bundle several unrelated capabilities into one GitHub App. A user may only need PR review, while the application requests permissions required for autonomous agents, workflow execution, branch modification, or other features.

Today the only choices are effectively “grant the vendor everything it requested” or “do not use the integration.” That prevents organizations from applying least privilege at the trust boundary where it actually matters: the resource owner.

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐