Skip to main content
We publish frequent updates to our documentation, and translation of this page may still be in progress. For the most current information, please visit the English documentation.
All products
Enterprise administrators

This version of GitHub Enterprise was discontinued on 2023-03-15. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.

Disabling unauthenticated sign-ups

In this article

If you're using built-in authentication for your GitHub Enterprise Server instance, you can block unauthenticated people from creating new user accounts on your instance.

Who can use this feature

Site administrators can disable unauthenticated sign-ups on a GitHub Enterprise Server instance.

About unauthenticated sign-ups

When you use built-in authentication for your GitHub Enterprise Server instance, each person creates a personal account from an invitation or by signing up. By default, people who can access your instance while unauthenticated can create a new personal account on your instance. You can disable unauthenticated sign-ups and require an invitation to create a new user account on your instance.

Alternatively, you can configure external authentication for your GitHub Enterprise Server instance. If you use external authentication, you must invite people to use your instance through your authentication provider. For more information, see "About authentication for your enterprise."

Disabling unauthenticated sign-ups

  1. From an administrative account on GitHub Enterprise Server, in the upper-right corner of any page, click .

  2. If you're not already on the "Site admin" page, in the upper-left corner, click Site admin.

  3. In the " Site admin" sidebar, click Management Console.

  4. In the "Settings" sidebar, click Privacy.

  5. Deselect Enable sign-up.

  6. Under the "Settings" sidebar, click Save settings.

    Note: Saving settings in the Management Console restarts system services, which could result in user-visible downtime.

  7. Wait for the configuration run to complete.