You can set visibility for new organization members across your enterprise to public or private. You can also prevent members from changing their visibility from the default.
You can prevent users from creating organizations in your enterprise.
You can require organization members and outside collaborators to enable two-factor authentication for their personal accounts in an organization, making it harder for malicious actors to access an organization's repositories and settings.
Teams give organizations the ability to create groups of members and control access to repositories. Team members can be granted read, write, or admin permissions to specific repositories.
Once a team has been created, organization admins can add users from your GitHub Enterprise Server instance to the team and determine which repositories they have access to.
You can manage your membership in any organization owned by your enterprise and change your role within the organization.
If a member of your organization no longer requires access to certain repositories, you can remove them from the team that allows that access. If a member of your organization no longer requires access to any repositories owned by the organization, you can remove them from the organization.
You can partially restore an organization that was previously deleted on your GitHub Enterprise Server instance.
You can integrate Jira with GitHub Enterprise Server for project management.
You can automatically trigger build jobs on a Jenkins server when pushes are made to a repository in your GitHub Enterprise Server instance.