title | shortTitle | intro | versions | type | topics | |||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Best practices for enterprises |
Best practices |
Learn {% data variables.product.company_short %}-recommended practices for your enterprise. |
|
overview |
|
{% ifversion ghec %}
Before you start using {% data variables.product.product_name %}, 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.
{% endif %}
{% data reusables.organizations.ent-ownership-recommendation %} {% ifversion ghec or ghes %}For more information, see AUTOTITLE.{% endif %}
We recommend using policies to enforce business rules and regulatory compliance.
{% data reusables.enterprise.about-policies %} For more information, see AUTOTITLE.
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.
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 %}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.
{% ifversion enterprise-readme %}
{% data reusables.enterprise.about-readmes %} For more information, see AUTOTITLE.
{% endif %}