Use policies
We recommend using policies to enforce business rules and regulatory compliance.
Each enterprise policy controls the options available for a policy at the organization level. You can choose to not enforce a policy, which allows organization owners to configure the policy for the organization, or you can choose from a set of options to enforce for all organizations owned by your enterprise. For more information, see "About enterprise policies."
Minimize the number of organizations
Large enterprises often need multiple organizations, but try to create as few as possible to reflect top-level corporate divisions. A smaller number of organizations encourages innersource practices and allows discussions to involve a wider audience.
Instead, you can manage repository access and security requirements at a more granular level within each organization by using teams. For more information, see "About teams."
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
Use 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 "Managing the display of member names in your organization."