# Using built-in authentication

If you don't use a centralized, external system for your users' identity, you can use built-in authentication to allow GitHub Enterprise Server to manage accounts and perform local authentication.

## Links

* [Configuring built-in authentication](/en/enterprise-server@3.22/admin/managing-iam/using-built-in-authentication/configuring-built-in-authentication)

  When you use the default authentication method, all authentication details are stored on GitHub.com.

* [Inviting people to use your instance](/en/enterprise-server@3.22/admin/managing-iam/using-built-in-authentication/inviting-people-to-use-your-instance)

  When you use built-in authentication for GitHub Enterprise Server, you can invite people by email address to create a user account on your instance.

* [Disabling unauthenticated sign-ups](/en/enterprise-server@3.22/admin/managing-iam/using-built-in-authentication/disabling-unauthenticated-sign-ups)

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

* [Disabling passkeys for your instance](/en/enterprise-server@3.22/admin/managing-iam/using-built-in-authentication/disabling-passkeys-for-your-instance)

  Learn how to disable passkeys for all users on your instance.