Groups of people can collaborate across many projects at the same time in organization accounts.
After you create your organization, you can add people as members of the organization. You can also remove members of the organization, and reinstate former members.
You can control access to your organizations's settings and repositories by giving people organization, repository, and team roles.
You can group organization members into teams that reflect your company or group's structure with cascading access permissions and mentions.
Within an organization, your team can work together across projects using team discussions.
Organization owners can manage individual and team access to the organization's repositories. Team maintainers can also manage a team's repository access.
As an organization owner or project board admin, you can give organization members, teams, and outside collaborators different levels of access to project boards owned by your organization.
As an organization owner, you can allow individual organization members to manage GitHub Apps in your organization.
Organization administrators can change several settings, including the names of repositories that belong to the organization and Owners team membership. In addition, organization admins can delete the organization and all of its repositories.
OAuth App access restrictions allow organization owners to restrict an untrusted app's access to the organization's data. Organization members can then use OAuth Apps for their personal user accounts while keeping organization data safe.
Organization owners have several features to help them keep their projects and data secure. If you're the owner of an organization, you should regularly review your organization's audit log, member 2FA status, and application settings to ensure that no unauthorized or malicious activity has occurred.
Organization administrators can manage organization members' identities and access to the organization with SAML single sign-on (SSO).
Organization administrators can grant access to their organization with SAML single sign-on. This access can be granted to organization members, bots, and service accounts.
You can add an SSH certificate authority (CA) to your organization and allow members to access the organization's repositories over Git using keys signed by the SSH CA.
If your organization was created after September 2015, your organization includes improved organization permissions by default. Organizations created before September 2015 may need to migrate older Owners and Admin teams to the improved organization permissions model.
All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.
Or, learn how to contribute.