[Merge after 21 Oct] Update enterprise concepts and best practices (#58020)

Co-authored-by: Greg Padak <gpadak@github.com>
Co-authored-by: Melanie Yarbrough <11952755+myarb@users.noreply.github.com>
Co-authored-by: Laura Coursen <lecoursen@github.com>
Co-authored-by: Hirsch Singhal <1666363+hpsin@users.noreply.github.com>

content/admin/concepts/best-practices-for-enterprises.md

@@ -1,67 +0,0 @@
----
-title: Best practices for enterprises
-shortTitle: Best practices
-intro: 'Learn {% data variables.product.company_short %}-recommended practices for your enterprise.'
-versions:
-  ghec: '*'
-  ghes: '*'
-contentType: concepts
-topics:
-  - Accounts
-  - Enterprise
-  - Fundamentals
-redirect_from:
-  - /admin/overview/best-practices-for-enterprises
----
-
-{% ifversion ghec %}
-
-## Choose an enterprise type
-
-Before you start using {% data variables.product.prodname_ghe_cloud %}, you must choose a type of enterprise. {% data reusables.enterprise.ghec-authentication-options %}
-
-For help identifying the type of enterprise that will best meet your needs, see [AUTOTITLE](/admin/identity-and-access-management/understanding-iam-for-enterprises/choosing-an-enterprise-type-for-github-enterprise-cloud).
-
-{% endif %}
-
-## Assign multiple owners
-
-{% data reusables.organizations.ent-ownership-recommendation %} For more information, see [AUTOTITLE](/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise).
-
-## Use policies
-
-We recommend using policies to enforce business rules and regulatory compliance.
-
-{% data reusables.enterprise.about-policies %} For more information, see [AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies).
-
-## Minimize the number of organizations
-
-Most businesses are best served by a single organization. Some enterprises may need multiple organizations for compliance or security reasons, but try to create as few as possible. A smaller number of organizations encourages innersource practice, allows discussions to involve a wider audience, and reduces administrative overhead.
-
-For more guidance on how many organizations to create and how to structure them, see [AUTOTITLE](/admin/user-management/managing-organizations-in-your-enterprise/best-practices-for-structuring-organizations-in-your-enterprise).
-
-## Avoid extensive collaboration in user-owned repositories
-
-We recommend collaborating in organization-owned repositories whenever possible and minimizing collaboration in user-owned repositories. Organization-owned repositories have more sophisticated security and administrative features, and they remain accessible even as enterprise membership changes.
-
-## Use human-readable usernames
-
-{% ifversion ghec %}If you control the usernames for enterprise members, use{% else %}Use{% endif %} human-readable usernames, and avoid machine-generated IDs that are difficult for humans to read.
-
-You can manage the display of usernames within your enterprise's private repositories. For more information, see [AUTOTITLE](/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization).
-
-{% ifversion enterprise-readme %}
-
-## Create a README
-
-{% data reusables.enterprise.about-readmes %} For more information, see [AUTOTITLE](/admin/managing-your-enterprise-account/creating-a-readme-for-an-enterprise).
-
-{% endif %}
-
-## Maintain ownership continuity
-
-Organizations can have more than one organization owner to avoid lapses in ownership. We recommend that at least two people within each organization have the owner role. For more information, see [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization).
-
-## Further reading
-
-* [AUTOTITLE](/organizations/collaborating-with-groups-in-organizations/best-practices-for-organizations)

content/admin/concepts/best-practices.md

@@ -0,0 +1,65 @@
+---
+title: Best practices for organizing work in your enterprise
+shortTitle: Best practices
+intro: Promote collaboration and manage resources at scale by following {% data variables.product.company_short %}-recommended practices for managing organizations and teams.
+versions:
+  ghec: '*'
+  ghes: '*'
+contentType: concepts
+topics:
+  - Accounts
+  - Enterprise
+  - Fundamentals
+redirect_from:
+  - /admin/overview/best-practices-for-enterprises
+  - /admin/user-management/managing-organizations-in-your-enterprise/best-practices-for-structuring-organizations-in-your-enterprise
+  - /admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/best-practices-for-structuring-organizations-in-your-enterprise
+  - /admin/concepts/best-practices-for-enterprises
+allowTitleToDifferFromFilename: true
+---
+
+## Use organizations for work or governance
+
+There are two main models of using organizations:
+
+* **Group related work projects**: Group repositories for a specific application and related services. Teams that work on that application will then be able to communicate effectively and contribute across the different repositories.
+* **Group similar governance requirements**: Group repositories that require similar policies, security settings, or access restrictions. You will be able to apply the necessary settings to the organization at scale. For example, if you have highly confidential work projects or a specific data classification, group these in an organization where only a limited number of people have access.
+
+## Create organizations intentionally
+
+Creating organizations is a balance. While {% data variables.product.company_short %} continues to make organization management more scalable, you should be intentional about why you create an organization. It's always easier to add organizations than to remove them.
+
+Don't try to fit unnatural pieces of your company together into a single large organization. The administrative features of an enterprise account allow you to automate processes, manage access, and apply policies across multiple organizations at once. However, there are tradeoffs of segregating work into many different organizations:
+
+* It's easier for people to communicate within one organization, as @-mentions only work between members of the same organization.
+* It's easier for people to find resources in one organization, as there's only one place to search.
+
+You may want to start with a small number of organizations as you develop your strategy. After you build confidence in what works well for your business, you can create additional organizations as the need arises.
+
+You should regularly evaluate your strategies for access, governance, and organization of work. Cleaning up legacy organizations is a part of that process.
+
+{% ifversion enterprise-teams %}
+
+## Use teams to organize people
+
+>[!NOTE] Enterprise teams are in public preview and subject to change.
+
+Enterprise teams are the best way to control access and permissions at scale. Create teams and manage their membership as your primary means of performing actions like adding users to organizations, granting licenses, and delegating access to enterprise settings.
+
+When you use teams in this way, controlling membership of teams is a sensitive action. Limit the permission to control teams and their membership to a small number of people. If you use an external identity provider (IdP), sync teams to IdP groups so that team membership can be controlled by a central administrator.
+
+Use roles to delegate administrative duties to teams. This allows you to limit the number of enterprise owners in your company and give people just the permissions they need to do their jobs effectively. For example, a team of auditors can receive access to the enterprise audit log without being able to access any other settings.
+
+{% endif %}
+
+## Collaborate in organization-owned repositories
+
+We recommend collaborating in organization-owned repositories whenever possible and minimizing collaboration in user-owned repositories. Organization-owned repositories have more sophisticated security and administrative features, and they remain accessible even as enterprise membership changes.
+
+{% ifversion ghec %}
+
+## Next steps
+
+Learn how to set up your enterprise according to best practices in our [AUTOTITLE](/enterprise-cloud@latest/enterprise-onboarding) journey for {% data variables.product.prodname_ghe_cloud %}.
+
+{% endif %}

content/admin/concepts/enterprise-fundamentals/enterprise-accounts.md

@@ -1,6 +1,6 @@
 ---
 title: Enterprise accounts
-intro: 'Learn how enterprise accounts enable scalability by simplifying administration and billing across multiple organizations.'
+intro: 'Get started with top-down administration by understanding the key components of an enterprise account.'
 redirect_from:
   - /articles/about-github-business-accounts
   - /articles/about-enterprise-accounts
@@ -11,6 +11,7 @@ redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts
   - /admin/overview/about-enterprise-accounts
   - /admin/managing-your-enterprise-account/about-enterprise-accounts
+  - /admin/overview/feature-overview-for-github-enterprise-cloud
 versions:
   ghec: '*'
   ghes: '*'
@@ -21,51 +22,83 @@ topics:
   - Fundamentals
 ---
 
-## What are enterprise accounts?
+An enterprise account is the central point of administration for your business on {% data variables.product.github %}. It brings together administrative tools for access management, policies, billing, and more. Enterprise administrators can set up features and policies efficiently at scale before deploying them across the business.
 
-<!-- expires 2026-01-30 -->
+This guide provides an overview of the major administrative features included in an enterprise account. By understanding the tools at your disposal, you will be able to adapt {% data variables.product.github %} to your unique needs, set your business up for future scaling, and enable teams to focus on strategic work.
 
-<!-- When this expires, check with the stakeholder for release #4079 on whether or not the content is still needed -->
+## Users
 
-{% ifversion ghec %}
+Your enterprise contains all the users who need to access any part of your company's resources on {% data variables.product.github %}. Users can be grouped into teams and given access to organizations.
-> [!NOTE] {% data variables.product.prodname_ghe_cloud %} customers who use a single organization are being automatically upgraded to an enterprise account at no additional cost. For details, see [AUTOTITLE](/admin/managing-your-enterprise-account/creating-an-enterprise-account#what-will-happen-after-i-upgrade-my-organization).
+
+{% ifversion ghes %}
+On {% data variables.product.prodname_ghe_server %}, you have a range of options for creating and authenticating user accounts, including built-in accounts or provisioning accounts from an identity provider.
+{% else %}
+Depending on your enterprise type, you will invite users into your enterprise with their existing {% data variables.product.github %} account, or provision dedicated accounts from a central identity provider.
 {% endif %}
 
-<!-- end expires 2026-01-30 -->
+By default, most users have a non-administrative role in your enterprise, which means they have little reason to interact with the enterprise account itself. However, you can change this by granting enterprise roles that provide access to specific settings.
 
-An enterprise account enables centralized management for **multiple organizations**.
+## Organizations
 
-Administrators for the enterprise account can:
+An enterprise account may contain one or more organizations. Like an enterprise account, an organization account contains its own administrative features such as audit logs, policies, and teams.
 
-* View and manage enterprise membership
+An organization also contains the places where non-admins typically do their work, such as repositories, discussions, and projects. The users in an organization are the people who need to access these places to do their jobs.
-* Manage billing and usage
-* Configure security, such as single sign-on, IP allow lists, SSH certificate authorities, and two-factor authentication
-* Stream audit and Git events data
-* Use internal repositories
-* Access features like {% data variables.copilot.copilot_enterprise %} and {% data variables.product.prodname_AS %}{% ifversion ghas-products %} products{% endif %}
-* Enforce policies. See [AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies).
 
-{% ifversion ghec %}
+Generally, you can govern organizations consistently from your enterprise account. To allow for more tailored and granular administration, you can also delegate some decisions, such as policy settings, to organization administrators.
 
-{% data reusables.enterprise.create-an-enterprise-account %} See [AUTOTITLE](/admin/managing-your-enterprise-account/creating-an-enterprise-account).
+{% ifversion enterprise-teams %}
+
+## Teams
+
+Teams are groups of users that you can use to manage people's access to organizations, roles, and licenses at scale. You can use teams to add people to shared projects or delegate duties to specialized teams.
+
+You can define teams at the enterprise level, then grant them administrative roles or add them to organizations, where they can receive organization-level roles and repository access.
+
+Teams can be synced with IdP groups, allowing you to manage any privileges that come with team membership directly from your company's centralized identity management system.
 
 {% endif %}
 
-## What if I use multiple deployment options?
+## Repositories
 
-If you use both {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}, you'll have **an enterprise account for each.**
+Repositories host files such as your company's source code or internal documentation. They are where developers typically do their work, and they contain their own features and administration options that need to live closer to the code, such as {% data variables.product.prodname_actions %} workflows.
 
-For the most part, you will manage each enterprise account separately. For example, you will configure the policies and settings for your {% data variables.product.prodname_ghe_server %} instance using the enterprise account on {% data variables.product.prodname_ghe_server %}.
+Repositories are owned by organizations and are not directly accessible under the enterprise account.{% ifversion custom-properties-enterprise %} However, your enterprise can define custom properties to apply the same governance model to all repositories with shared characteristics. For example, if you do not want anyone to delete repositories that contain production code, this is something you can govern from the enterprise level.{% endif %}
 
-However, you can also use the enterprise account on {% data variables.product.prodname_ghe_cloud %} to view all license usage across all deployments. This allows you to ensure people with accounts in both environments only consume one user license. See [AUTOTITLE](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud).
+{% ifversion ghec %}
 
-## What if I only use {% data variables.product.prodname_ghe_server %}?
+## Cost centers
 
-Even if you **only** use {% data variables.product.prodname_ghe_server %}, we recommend creating an enterprise account on {% data variables.product.prodname_ghe_cloud %}. This will make it easier to contact {% data variables.contact.enterprise_support %} and share support bundles with them.
+Cost centers allow you to allocate spending on {% data variables.product.github %} features to specific business units. They let you define your billing structure independently from other parts of the enterprise, so you can focus on using organization accounts to group related work or governance requirements.
 
-To create an additional enterprise account on {% data variables.product.prodname_ghe_cloud %}, contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
+If your account is billed through Azure, cost centers also allow you to bill usage to multiple different Azure subscriptions.
 
-## Further reading
+## Policies
 
-* [AUTOTITLE](/graphql/guides/managing-enterprise-accounts) in the GraphQL API documentation {% ifversion ghec %}
+Enterprise administrators can set policies to govern how people work across your enterprise, such as:
-* [AUTOTITLE](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise){% endif %}
+
+* IP allow lists to enforce restrictions on where people can access your enterprise
+* {% data variables.product.prodname_copilot_short %} policies to govern which features and models people can use
+* Repository policies to control who can do things like delete, rename, or transfer repositories
+* Rulesets to define how people can interact with important branches, such as requiring pull requests with reviews
+
+{% endif %}
+
+{% ifversion enterprise-apps-public-beta %}
+
+## Apps
+
+{% data variables.product.prodname_github_apps %} are a secure way to manage automations across your enterprise. A {% data variables.product.prodname_github_app %} is a dedicated identity that provides scoped tokens to your external scripts and workflows, allowing you to automate processes and integrate with other platforms.
+
+In your enterprise account, you can define app registrations to automate a process consistently across organizations.{% ifversion enterprise-installed-apps %} You can also install apps for automations that take actions on the enterprise account itself, such as creating organizations.{% endif %}
+
+Users can also authorize {% data variables.product.prodname_github_apps %} to use their {% data variables.product.github %} account and data in other applications—for example, to use their {% data variables.product.github %} account to sign in to an IDE or connect a CI provider to your repositories.
+
+{% endif %}
+
+{% ifversion ghec %}
+
+## Next steps
+
+Learn how to set up these features with our [AUTOTITLE](/enterprise-cloud@latest/enterprise-onboarding) journey for {% data variables.product.prodname_ghe_cloud %}.
+
+{% endif %}

content/admin/concepts/enterprise-fundamentals/teams-in-an-enterprise.md

@@ -1,6 +1,6 @@
 ---
 title: Teams in an enterprise
-intro: 'Learn how teams simplify administration of user access, licensing, and communication.'
+intro: 'Simplify administration of user access, licensing, and communication with teams.'
 versions:
   feature: enterprise-teams
 shortTitle: Teams

content/admin/concepts/index.md

@@ -1,7 +1,7 @@
 ---
 title: Concepts for enterprises
 shortTitle: Concepts
-intro: 'Learn the core concepts that you''ll need to understand {% data variables.location.product_location %}.'
+intro: Learn the core concepts that you'll need to understand {% data variables.location.product_location %}.
 versions:
   ghes: '*'
   ghec: '*'
@@ -11,6 +11,7 @@ children:
   - /enterprise-fundamentals
   - /identity-and-access-management
   - /security-and-compliance
-  - /best-practices-for-enterprises
+  - /best-practices
 contentType: concepts
 ---
+

content/admin/data-residency/feature-overview-for-github-enterprise-cloud-with-data-residency.md

@@ -12,7 +12,7 @@ redirect_from:
 
 ## Available features
 
-{% data variables.product.prodname_ghe_cloud %} is a developer platform that supports the entire software development lifecycle, including planning work, automating tests and deployments, and keeping code secure. To learn about available features, see [AUTOTITLE](/enterprise-cloud@latest/admin/overview/feature-overview-for-github-enterprise-cloud).
+{% data variables.product.prodname_ghe_cloud %} is a developer platform that supports the entire software development lifecycle, including planning work, automating tests and deployments, and keeping code secure. To learn about available features, see [{% data variables.product.company_short %}'s plans page](https://github.com/pricing).
 
 ## Currently unavailable features
 

content/admin/index.md

@@ -74,7 +74,6 @@ featuredLinks:
     - '/admin/concepts/identity-and-access-management\identity-and-access-management-fundamentals'
     - '{% ifversion ghec %}/admin/concepts/identity-and-access-management/enterprise-types-for-github-enterprise-cloud{% endif %}'
     - '{% ifversion ghec %}/admin/managing-accounts-and-repositories/managing-roles-in-your-enterprise/abilities-of-roles{% endif %}'
-    - /admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/best-practices-for-structuring-organizations-in-your-enterprise
     - '{% ifversion ghes %}/admin/getting-started-with-enterprise/about-upgrades-to-new-releases{% endif %}'
     - '{% ifversion ghes %}/billing/how-tos/set-up-payment/manage-enterprise-invoice{% endif %}'
   guideCards:

content/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/best-practices-for-structuring-organizations-in-your-enterprise.md

@@ -1,91 +0,0 @@
----
-title: Best practices for structuring organizations in your enterprise
-intro: 'Learn to identify how many organizations to create within your enterprise, and how you should structure them.'
-versions:
-  ghec: '*'
-  ghes: '*'
-type: overview
-topics:
-  - Administrator
-  - Enterprise
-  - Organizations
-shortTitle: Best practices
-redirect_from: 
-  - /admin/user-management/managing-organizations-in-your-enterprise/best-practices-for-structuring-organizations-in-your-enterprise
----
-
-## About best practices for organizations within an enterprise
-
-There are a multiple options for structuring the organizations within your enterprise. Each approach has pros and cons, and the best structure for your enterprise depends on the characteristics and needs of your business, including size and security constraints.
-
-However, we also recommend aligning your strategy with the culture you want to create, not the culture you currently have. If you want to advance in terms of collaboration and innersourcing, structure your tools accordingly. Then, your tools can assist you in the cultural change instead of acting as a blocker.
-
-## About organizational number
-
-In general, {% data variables.product.company_short %} recommends minimizing the number of organizations you create. Having fewer organizations encourages greater collaboration and innersourcing, which increases efficiency. In fact, many businesses are best served by a single organization, for the following reasons.
-
-* It's easier to find resources within a single organization, as there's only one place to search.
-* It's easier to communicate within a single organization, as @-mentions only work between members of the same organization.
-* Being part of a single, large organization where anyone and anything is accessible fosters collaboration and loyalty, whereas being separated into smaller organizations can make teams more isolated.
-
-Organization owners always have access to all repositories owned by the organization. If your company is large enough that no single owner should have access to all repositories, consider creating multiple organizations.
-
-The main benefit of creating multiple organizations is the ability to configure separate policies, settings, and requirements for each. {% ifversion ghec %} For example, each organization can have a different SAML configuration.{% endif %}
-
-Avoid creating a one-to-one relationship between organizations and structural entities of your company, such as individual teams or business units. Instead, group structural entities that can share policies, settings, and requirements into a single organization. This approach maximizes collaboration while meeting your regulatory requirements.
-
-It’s always easier to add organizations than to remove them, so we recommend starting with a small number of organizations, which gives you more flexibility in the future. After you develop more experience of what works well for your business, you can create additional organizations if the need arises.
-
-Removing organizations is much more difficult, often requiring migrations and a reduction in flexibility that teams have gotten used to. Many customers have come to regret creating a large number of organizations after they experience the challenging and time-consuming process of reducing their number.
-
-We recommend creating and enforcing fixed and transparent rules for creating a new organization in your enterprise. This will make it easier for everyone to understand the purpose of each organization and which assets are located where.
-
-## About organizational structure
-
-There are five main archetypes for organizational structure. The archetypes are defined by two decisions:
-
-* Whether to use a single organization or multiple organizations
-* Whether to grant all members access to all repositories, or use teams to manage repository access more granularly
-
-For more information about teams, see [AUTOTITLE](/organizations/organizing-members-into-teams/about-teams).
-
-### Single organization with direct repository access
-
-The simplest organizational structure is a single organization, where members are granted access to all repositories directly via organization membership. Teams may be used for coordination and communication, but not for managing repository access.
-
-This structure works best for small companies, such as startups, where everyone collaborates on everything. It can work for medium-sized companies as well, if trust is high.
-
-To use this archetype, set the base permissions for the organization to "Write" or "Read." For more information, see [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/setting-base-permissions-for-an-organization).
-
-### Single organization with teams for repository access
-
-If your company needs to control repository access more granularly, you can set the base permissions for your organization to "None," then give each team access to specific repositories only.
-
-This structure works best for medium-sized companies, or for small companies with lower trust. For smaller companies with high trust, where everyone collaborates on everything, administering teams may not be worth the time investment.
-
-### Multiple organizations with direct repository access
-
-For larger companies, managing repository access within a single organization can become unwieldy, even with teams. This archetype utilizes multiple organizations to manage repository access instead. Each organization's members have access to all of that organization's repositories.
-
-This structure works best for companies that are large enough to have different groups that don't need to work together. This structure is not as useful if collaboration across business units is important.
-
-To use this archetype, create one organization for each group that can share policies, settings, and requirements as described above, then set the base permissions for each organization to "Write" or "Read."
-
-### Multiple organizations with teams for repository access
-
-Very large companies may require more granular control over repository access, even within multiple organizations. In this case, you can use teams to give each group access to specific repositories only.
-
-To use this archetype, create one organization for each group that can share policies, settings, and requirements as described above, set the base permission for each organization to "None," then give each team access to specific repositories only.
-
-### Multiple organizations with different access methods
-
-If you want the collaboration benefits of a single organization with direct repository access, but you have a small number of repositories that are too sensitive for global access, consider using multiple organizations with a mix of access methods.
-
-To use this archetype, create one organization for all of your employees and most of your repositories. Grant all members access to all repositories in this organization by setting the base permissions for the organization to "Write" or "Read."
-
-Then, create a second organization specifically for more sensitive repositories. In this organization, set the base permissions to "None", add only the people that need to access the sensitive repositories, and manage access to the repositories via team membership.
-
-## Further reading
-
-* [Organize your experts with ad hoc teams](https://github.blog/2017-02-15-organize-your-experts-with-ad-hoc-teams/) in the {% data variables.product.company_short %} blog
-* [AUTOTITLE](/organizations/collaborating-with-groups-in-organizations/best-practices-for-organizations)

content/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/index.md

@@ -20,7 +20,6 @@ versions:
 topics:
   - Enterprise
 children:
-  - /best-practices-for-structuring-organizations-in-your-enterprise
   - /adding-organizations-to-your-enterprise
   - /configuring-visibility-for-organization-membership
   - /preventing-users-from-creating-organizations

content/admin/managing-accounts-and-repositories/managing-repositories-in-your-enterprise/managing-custom-properties-for-repositories-in-your-enterprise.md

@@ -3,7 +3,7 @@ title: Managing custom properties for repositories in your enterprise
 intro: 'Create custom properties to give organizations a consistent way to categorize repositories.'
 permissions: Enterprise owners
 versions:
-  ghec: '*'
+  feature: custom-properties-enterprise
 topics:
   - Repositories
 shortTitle: Custom properties

content/admin/managing-accounts-and-repositories/managing-roles-in-your-enterprise/abilities-of-roles.md

@@ -1,6 +1,6 @@
 ---
 title: Abilities of roles in an enterprise
-intro: Learn which roles you can assign to control access to your enterprise's settings and data.
+intro: Find the right role to grant access to your enterprise's settings and data.
 shortTitle: Predefined roles
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise

content/admin/managing-accounts-and-repositories/managing-roles-in-your-enterprise/assign-roles.md

@@ -1,6 +1,6 @@
 ---
 title: Assigning roles to people in an enterprise
-intro: Assign roles to users and teams to govern what people can do in your enterprise.
+intro: Govern what people can do in your enterprise by assigning roles to users and teams.
 versions:
   feature: enterprise-custom-roles
 type: how_to

content/admin/managing-github-apps-for-your-enterprise/creating-github-apps-for-your-enterprise.md

@@ -56,4 +56,10 @@ For apps that require installation to function, you can provide organization own
 
 If your {% data variables.product.prodname_github_app %} requires installation (not just authorization), organization owners can use the install link to install the app on their organization. See [AUTOTITLE](/apps/using-github-apps/installing-a-github-app-from-a-third-party).
 
-{% ifversion enterprise-installed-apps %}If your app uses enterprise permissions, you can install it on your enterprise. To find the installation link, go to the app's settings page in your enterprise account. See [AUTOTITLE](/apps/using-github-apps/installing-a-github-app-on-your-enterprise).{% endif %}
+{% ifversion enterprise-installed-apps %}
+
+If you need to install the same app in many organizations, you can automate this with an API. See [AUTOTITLE](/admin/managing-github-apps-for-your-enterprise/automate-installations).
+
+If your app uses enterprise permissions, you can install it on your enterprise. To find the installation link, go to the app's settings page in your enterprise account. See [AUTOTITLE](/apps/using-github-apps/installing-a-github-app-on-your-enterprise).
+
+{% endif %}

content/admin/overview/about-github-for-enterprises.md

@@ -10,11 +10,12 @@ topics:
   - Fundamentals
 ---
 
-## Why should my business choose {% data variables.product.prodname_dotcom %}?
+## Why should my business choose {% data variables.product.github %}?
 
-* **Provide a platform developers already know.** Adopting {% data variables.product.prodname_dotcom %} can help you reduce onboarding time, attract talent, and leverage a large open source community by using tools already familiar to more than 100 million developers.
+* **Provide a platform developers already know.** Adopting {% data variables.product.github %} can help you attract talent, reduce onboarding time, and leverage a large open source community by using tools already familiar to more than 100 million developers.
-* **Consolidate tools in the cloud.** {% data variables.product.prodname_dotcom %} is a complete developer platform to build, scale, and deliver secure software. Adopting {% data variables.product.prodname_dotcom %} can help companies consolidate their DevOps tools or move away from on-premises solutions that can be difficult to maintain.
+* **Consolidate tools in the cloud.** {% data variables.product.github %} is a complete developer platform to build, scale, and deliver secure software. Adopting {% data variables.product.github %} can help companies consolidate their DevOps tools or move away from on-premises solutions that can be difficult to maintain.
-* **Benefit from modern features.** {% data variables.product.company_short %} consistently releases new features and updates. Our platform includes well-known tools like {% data variables.product.prodname_copilot %} and {% data variables.product.prodname_actions %}.
+* **Integrate with AI.** {% data variables.product.github %} provides AI tools to boost productivity at every stage of the development lifecycle. Your developers can work with AI agents to plan, prototype, code, review work, and fix vulnerabilities.
+* **Govern at scale.** {% data variables.product.github %} provides advanced governance features and a central point of administration for development work across your business. Set up projects and manage access in a way that meets your complex needs and allows for future scaling.
 
 ## How enterprises use {% data variables.product.prodname_dotcom %}
 
@@ -61,9 +62,9 @@ Your business can:
 
 {% data variables.product.prodname_enterprise %} is our most comprehensive plan. In addition to the features included with a {% data variables.product.prodname_free_team %} or {% data variables.product.prodname_team %} plan for organizations, the plan includes:
 
+* An enterprise account, which provides a single place to manage teams, grant access, enforce policies, and audit activity.
 * Additional features such as SAML authentication and internal repositories. For a detailed list, see {% data variables.product.pricing_link %}.
 * Extra allowances for usage-based products such as {% data variables.product.prodname_actions %}.
-* An enterprise account, which provides a single place to manage billing and settings, enforce policies, and audit the people with access to your enterprise.
 * The option to add {% ifversion ghas-products %}<!-- Enterprise is no longer a pre-requisite with the GHAS products release -->{% else %}{% data variables.product.prodname_GHAS %}, {% endif %}{% data variables.contact.premium_support %}, and {% data variables.copilot.copilot_enterprise %}.
 
 When businesses adopt {% data variables.product.prodname_enterprise %}, their return on investment (ROI) is high. For example, their developers **save 45 minutes per day**, and onboarding and **training time is reduced by 40%**. See [The Total Economic Impact of {% data variables.product.prodname_enterprise %}](https://resources.github.com/forrester/).
@@ -84,22 +85,10 @@ When businesses adopt {% data variables.product.prodname_enterprise %}, their re
 * You create accounts for users, and authenticate users using either built-in authentication or an external system.
 * You can enable {% data variables.product.prodname_github_connect %} to benefit from features that rely on {% data variables.product.prodname_dotcom_the_website %}, such as {% data variables.product.prodname_dependabot_alerts %} and actions hosted on {% data variables.product.prodname_dotcom_the_website %}.
 
+{% ifversion ghec %}
+
 ## Next steps
 
-1. Learn more about {% data variables.product.prodname_enterprise %}.
+Get started with our [AUTOTITLE](/enterprise-cloud@latest/enterprise-onboarding) journey for {% data variables.product.prodname_ghe_cloud %}.
 
-   * [AUTOTITLE](/enterprise-cloud@latest/admin/overview/about-github-enterprise-cloud){% ifversion ghes %} in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}
+{% endif %}
-   * [AUTOTITLE]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/overview/about-github-enterprise-server){% ifversion ghec %} in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}.{% endif %}
-1. Set up a trial.
-
-   * [AUTOTITLE](/admin/overview/setting-up-a-trial-of-github-enterprise-cloud)
-   * [AUTOTITLE](/admin/overview/setting-up-a-trial-of-github-enterprise-server)
-
-## Further reading
-
-* [AUTOTITLE](/admin/overview/about-enterprise-accounts)
-* [AUTOTITLE](/enterprise-cloud@latest/admin/data-residency/about-github-enterprise-cloud-with-data-residency){% ifversion ghes %} in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}
-* [AUTOTITLE](/get-started/learning-about-github/about-github-advanced-security)
-* [AUTOTITLE](/support/learning-about-github-support/about-github-premium-support)
-* [AUTOTITLE](/enterprise-server@latest/admin/configuration/configuring-github-connect/about-github-connect)
-* [Compare {% data variables.product.prodname_dotcom %} to other DevOps solutions](https://resources.github.com/devops/tools/compare/) in {% data variables.product.company_short %} Resources

content/admin/overview/feature-overview-for-github-enterprise-cloud.md

@@ -1,45 +0,0 @@
----
-title: Feature overview for GitHub Enterprise Cloud
-intro: 'Make the most of {% data variables.product.prodname_ghe_cloud %} by learning about its features.'
-shortTitle: Feature overview
-versions:
-  ghec: '*'
-type: overview
-topics:
-  - Enterprise
-  - Fundamentals
----
-
-{% data variables.product.prodname_ghe_cloud %} is a developer platform that supports the entire software development lifecycle, including planning work, automating tests and deployments, and keeping code secure.
-
-This article provides an overview and links to more information for some of {% data variables.product.github %}'s major features.
-
-## Features for administrators
-
-| Goal | More information |
-| :- | :- |
-| View people in your enterprise | [AUTOTITLE](/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/viewing-people-in-your-enterprise) |
-| Implement governance and enforce policies | [AUTOTITLE](/admin/policies/enforcing-policies-for-your-enterprise) |
-| Communicate information to users | [AUTOTITLE](/admin/managing-accounts-and-repositories/communicating-information-to-users-in-your-enterprise)
-| Introduce continuous integration and continuous deployment (CI/CD) at scale | [AUTOTITLE](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise) |
-| Ensure code quality and security at scale | [AUTOTITLE](/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale) |
-| Audit, understand, and troubleshoot user activity | [AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise) |
-
-## Features for developers
-
-| Goal | More information |
-| :- | :- |
-| Store and collaborate on code | <ul><li>[AUTOTITLE](/repositories/creating-and-managing-repositories/about-repositories)</li><li>[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)</li><li>[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/getting-started/best-practices-for-pull-requests)</li></ul> |
-| Protect important branches in repositories | [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets) |
-| Organize and manage access to repositories | <ul><li>[AUTOTITLE](/organizations/collaborating-with-groups-in-organizations/about-organizations)</li><li>[AUTOTITLE](/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/best-practices-for-structuring-organizations-in-your-enterprise)</li><li>[AUTOTITLE](/organizations/organizing-members-into-teams/about-teams)</li></ul> |
-| Receive, customize, triage, and manage updates about activity | [AUTOTITLE](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications) |
-| Format and structure text in comments | [AUTOTITLE](/get-started/writing-on-github) |
-| Search for code | [AUTOTITLE](/search-github/github-code-search/using-github-code-search) |
-| Configure continuous integration and continuous delivery (CI/CD) using {% data variables.product.prodname_actions %}  | <ul><li>[AUTOTITLE](/actions/automating-builds-and-tests/about-continuous-integration)</li><li>[AUTOTITLE](/actions/deployment/about-deployments/about-continuous-deployment)</li></ul> |
-| Improve code quality and security | [AUTOTITLE](/get-started/learning-about-github/about-github-advanced-security#about-advanced-security-features) |
-| Plan and track work | <ul><li>[AUTOTITLE](/issues/tracking-your-work-with-issues/about-issues)</li><li>[AUTOTITLE](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)</li></ul> |
-| Subscribe to events using webhooks | [AUTOTITLE](/webhooks/using-webhooks/creating-webhooks) |
-| Extend, customize, and automate | [AUTOTITLE](/rest/overview/comparing-githubs-rest-api-and-graphql-api) |
-| Triage, collaborate, and manage work using a desktop application | [AUTOTITLE](/desktop/overview/about-github-desktop) |
-| Triage, collaborate, and manage work using a mobile application | [AUTOTITLE](/get-started/using-github/github-mobile) |
-| Triage, collaborate, and manage work using the command-line interface | [AUTOTITLE](/github-cli/github-cli/about-github-cli) |

content/admin/overview/index.md

@@ -10,7 +10,6 @@ children:
   - /about-github-for-enterprises
   - /about-github-enterprise-cloud
   - /setting-up-a-trial-of-github-enterprise-cloud
-  - /feature-overview-for-github-enterprise-cloud
   - /about-github-enterprise-server
   - /setting-up-a-trial-of-github-enterprise-server
   - /about-upgrades-to-new-releases

content/apps/using-github-apps/installing-a-github-app-on-your-enterprise.md

@@ -67,6 +67,8 @@ Enterprise installations do not currently support webhooks. Apps installed at th
 
 Enterprise installations are not granted access to organizations or repositories within your enterprise, with the exception of the organization installations API. To access organization or repository resources, you must install the app separately on each organization where access is needed.
 
+If you need to install the same app in many organizations, you can automate this with an API. See [AUTOTITLE](/admin/managing-github-apps-for-your-enterprise/automate-installations).
+
 ## Next steps
 
 * To grant the app access to specific organizations, install it on those organizations. For more information, see [AUTOTITLE](/apps/using-github-apps/installing-a-github-app-from-a-third-party).

content/billing/concepts/enterprise-billing/combined-enterprise-use.md

@@ -15,10 +15,16 @@ redirect_from:
 contentType: concepts
 ---
 
-## About licensing for {% data variables.product.prodname_enterprise %}
+## About enterprise deployments
 
 {% data reusables.enterprise.about-deployment-methods %}
 
+If you use both {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}, you'll have **an enterprise account for each.** Even if you **only** use {% data variables.product.prodname_ghe_server %}, we recommend creating an enterprise account on {% data variables.product.prodname_ghe_cloud %}. This will make it easier to contact {% data variables.contact.enterprise_support %} and share support bundles with them. To create an additional enterprise account, contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
+
+For most administration options, such as policies, you will manage each enterprise account separately. However, you can use the enterprise account on {% data variables.product.prodname_ghe_cloud %} to view all license usage across all deployments.
+
+## About licensing for {% data variables.product.prodname_enterprise %}
+
 {% data reusables.enterprise-licensing.unique-user-licensing-model %}
 
 To use a {% data variables.product.prodname_ghe_server %} instance, you must upload a license file that {% data variables.product.company_short %} provides. See [AUTOTITLE](/billing/concepts/enterprise-billing/ghes-license-files).

content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md

@@ -177,7 +177,3 @@ For more information, see [AUTOTITLE](/get-started/start-your-journey/git-and-gi
 {% data reusables.getting-started.contact-support %}
 
 {% data variables.product.prodname_ghe_cloud %} allows you to submit priority support requests with a target eight-hour response time. For more information, see [AUTOTITLE](/support/learning-about-github-support/about-github-support).
-
-## Further reading
-
-* [AUTOTITLE](/enterprise-cloud@latest/admin/overview/feature-overview-for-github-enterprise-cloud)

data/features/custom-properties-enterprise.yml

@@ -0,0 +1,3 @@
+# Repository custom properties defined at the enterprise level
+versions:
+  ghec: '*'