Controlling who can request apps for your organization is now generally available #183833
ebndev
announced in
Announcements
Replies: 4 comments 2 replies
-
|
Is there going to be REST API support for this feature? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
This improvement is good, thanks. I wonder if this could be a little more fine-grained and restrict which groups/roles/users have permission to request apps. In large orgs, things can become noisy when everyone has permission to request. Thank you. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Nice feature |
Beta Was this translation helpful? Give feedback.
0 replies
-
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Organizations now have more granular control over who can request GitHub Apps and OAuth apps. This enhancement helps you implement stricter governance policies while maintaining flexibility for your security posture. This capability is now generally available.
What's changed
Previously, organizations could only disable app access requests from outside collaborators. Now, you can choose from three graduated control options:
To configure this change, navigate to your organization's settings, select Member Privileges, and choose your preferred option under "App access requests". This graduated control mechanism ensures all third-party apps go through proper approval channels and security reviews before being considered for installation.
To learn more, see "Limiting app requests". This will be included in GHES 3.21.
How to give feedback
If you have any questions or feedback, drop a comment in our Community discussion.
Beta Was this translation helpful? Give feedback.
All reactions