Your team can collaborate on GitHub by using an organization account, which serves as a container for your shared work and gives the work a unique name and brand.
Each person that uses GitHub always signs into a personal account, and multiple personal accounts can collaborate on shared projects by joining the same organization account. A subset of these personal accounts can be given the role of organization owner, which allows those people to granularly manage access to the organization's resources using sophisticated security and administrative features. For more information about account types, see "Types of GitHub accounts."
You can invite an unlimited number of people to join your organization, then give these organization members a variety of roles that grant different levels of access to the organization and its data. For more information, see "Roles in an organization."
In addition to managing access to the organization itself, you can separately manage access to your organization's repositories, project boards, and apps. For more information, see "Repository roles for an organization", "Project (classic) permissions for an organization", and "Managing programmatic access to your organization."
To simplify access management and enhance collaboration, you can create nested teams that reflect your group's structure, with cascading access permissions and mentions. For more information, see "About teams."
You can configure the organization to meet the unique needs of your group by managing settings, such as restricting the types of repositories that members can create. For more information, see "Managing organization settings."
To harden your organization's security, you can enforce security requirements and review the organization's audit log. For more information, see "Keeping your organization secure."
To learn how to use organizations most effectively, see "Best practices for organizations."
All organizations can own an unlimited number of public and private repositories. You can use organizations for free, with GitHub Free, which includes limited features on private repositories. To get the full feature set on private repositories and additional features at the organization level, including SAML single sign-on and improved support coverage, you can upgrade to GitHub Team or GitHub Enterprise Cloud. For more information, see "GitHub’s plans."
For more information about how you can try GitHub Enterprise Cloud for free, see "Setting up a trial of GitHub Enterprise Cloud."
Enterprise accounts are a feature of GitHub Enterprise Cloud that allow owners to centrally manage policy and billing for multiple organizations. For more information, see the GitHub Enterprise Cloud documentation.
An entity, such as a company, non-profit, or group, can agree to the Standard Terms of Service or the GitHub Customer Agreement for their organization. For more information, see "Upgrading to the GitHub Customer Agreement."