You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The general availability of enterprise-owned GitHub Apps brings several updates based on feedback from the public preview.
Most significantly, organizations and users can now transfer private visibility Apps to their enterprise, where they will become usable by the entire enterprise.
In addition, permission updates made to an enterprise-owned App are now automatically accepted by all of the organizations in the enterprise.
These updates allow enterprise owners to consolidate multiple per-organization Apps into a single registration that is managed efficiently at the enterprise level.
For enterprise-managed (EMU) users and organizations, both private and internal Apps can be transferred to the enterprise. Private Apps are those that only the owning account can use, while internal Apps are those that any organization and user in the enterprise can use. However, Enterprise Classic organizations and standard user accounts can only transfer private Apps, as internal Apps are not supported in Enterprise Classic.
At this time, internal is the only visibility setting allowed for enterprise-owned Apps, which means that only organizations in that enterprise can install it, and only users in the enterprise can authorize it. Any App that is transferred to an enterprise will be updated to be internal and uninstalled from the user account that owned it, if applicable.
To reduce abuse vectors, enterprises cannot transfer Apps to another enterprise, and organizations and users cannot transfer an App to an enterprise that they are not part of.
As in the preview, only an enterprise owner can manage Apps owned by the enterprise. However, we are actively working on App manager roles and permissions that will allow users and teams to manage specific Apps, as well as manage all of the Apps in an enterprise. These new fine-grained permissions will be introduced for both the enterprise and the organization—keep an eye out for these in the middle of the year.
For more information about enterprise-owned Apps, see our docs page. These updates will be available in GHES 3.17.
Let us know your thoughts, questions, and feedback below ⬇️
👂 Feedback WantedGitHub is asking for your feedback🚀 ShippedA feature has been released📣 ANNOUNCEMENTAnnouncements from the GitHub Community teamEnterpriseDiscussions related to GitHub Enterprise Cloud and Enterprise ServerChangelogA discussion post associated with a Changelog post
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The general availability of enterprise-owned GitHub Apps brings several updates based on feedback from the public preview.
Most significantly, organizations and users can now transfer
private
visibility Apps to their enterprise, where they will become usable by the entire enterprise.In addition, permission updates made to an enterprise-owned App are now automatically accepted by all of the organizations in the enterprise.
These updates allow enterprise owners to consolidate multiple per-organization Apps into a single registration that is managed efficiently at the enterprise level.
For enterprise-managed (EMU) users and organizations, both
private
andinternal
Apps can be transferred to the enterprise. Private Apps are those that only the owning account can use, whileinternal
Apps are those that any organization and user in the enterprise can use. However, Enterprise Classic organizations and standard user accounts can only transferprivate
Apps, asinternal
Apps are not supported in Enterprise Classic.At this time,
internal
is the only visibility setting allowed for enterprise-owned Apps, which means that only organizations in that enterprise can install it, and only users in the enterprise can authorize it. Any App that is transferred to an enterprise will be updated to beinternal
and uninstalled from the user account that owned it, if applicable.To reduce abuse vectors, enterprises cannot transfer Apps to another enterprise, and organizations and users cannot transfer an App to an enterprise that they are not part of.
As in the preview, only an enterprise owner can manage Apps owned by the enterprise. However, we are actively working on App manager roles and permissions that will allow users and teams to manage specific Apps, as well as manage all of the Apps in an enterprise. These new fine-grained permissions will be introduced for both the enterprise and the organization—keep an eye out for these in the middle of the year.
For more information about enterprise-owned Apps, see our docs page. These updates will be available in GHES 3.17.
Let us know your thoughts, questions, and feedback below ⬇️
Beta Was this translation helpful? Give feedback.
All reactions