# Enterprise administrator documentation Documentation and guides for enterprise administrators and security specialists who configure and manage GitHub Enterprise. ## Recommended * [About GitHub Enterprise Cloud](/en/enterprise-server@3.22/admin/overview/about-github-enterprise-cloud) Learn about GitHub Enterprise Cloud, its features, and management options for large businesses and teams. * [Enterprise accounts](/en/enterprise-server@3.22/admin/concepts/enterprise-fundamentals/enterprise-accounts) Get started with top-down administration by understanding the key components of an enterprise account. * [Identity and access management fundamentals](/en/enterprise-server@3.22/admin/concepts/identity-and-access-management/identity-and-access-management-fundamentals) Administrators must decide how users will access the enterprise's resources on GitHub. * [About Enterprise Managed Users](/en/enterprise-server@3.22/admin/concepts/identity-and-access-management/enterprise-managed-users) Learn how your enterprise can manage the lifecycle and authentication of users on GitHub from your identity provider (IdP). * [Audit log for an enterprise](/en/enterprise-server@3.22/admin/concepts/security-and-compliance/audit-log-for-an-enterprise) To support debugging and internal and external compliance, GitHub provides logs of audited user, organization, and repository events. * [Accessing compliance reports for your enterprise](/en/enterprise-server@3.22/admin/overview/accessing-compliance-reports-for-your-enterprise) You can access GitHub's compliance reports, such as our SOC reports and Cloud Security Alliance CAIQ self-assessment (CSA CAIQ), for your enterprise. ## Articles * [About GitHub for enterprises](/en/enterprise-server@3.22/admin/overview/about-github-for-enterprises) Learn about GitHub's enterprise products and deployment options for GitHub Enterprise. * [About GitHub Enterprise Server](/en/enterprise-server@3.22/admin/overview/about-github-enterprise-server) Find out if GitHub Enterprise Server is right for your business. * [Setting up a trial of GitHub Enterprise Server](/en/enterprise-server@3.22/admin/overview/setting-up-a-trial-of-github-enterprise-server) You can try GitHub Enterprise Server for free. * [About upgrades to new releases](/en/enterprise-server@3.22/admin/overview/about-upgrades-to-new-releases) Learn about how features and bug fixes are added to GitHub Enterprise Server through new releases. * [System overview](/en/enterprise-server@3.22/admin/overview/system-overview) Learn more about GitHub Enterprise Server's system internals, functionality, and security. * [About the GitHub Enterprise API](/en/enterprise-server@3.22/admin/overview/about-the-github-enterprise-api) GitHub Enterprise Server supports REST and GraphQL APIs. * [Establishing a governance framework for your enterprise](/en/enterprise-server@3.22/admin/overview/establishing-a-governance-framework-for-your-enterprise) You can manage governance and compliance for your enterprise using features and tools available in GitHub Enterprise. * [Enterprise accounts](/en/enterprise-server@3.22/admin/concepts/enterprise-fundamentals/enterprise-accounts) Get started with top-down administration by understanding the key components of an enterprise account. * [Teams in an enterprise](/en/enterprise-server@3.22/admin/concepts/enterprise-fundamentals/teams-in-an-enterprise) Simplify administration of user access, licensing, and communication with teams. * [Roles in an enterprise](/en/enterprise-server@3.22/admin/concepts/enterprise-fundamentals/roles-in-an-enterprise) Learn how roles allow you to control people's access to your enterprise's settings and resources. * [Automations in your enterprise](/en/enterprise-server@3.22/admin/concepts/enterprise-fundamentals/automations-in-your-enterprise) Learn how GitHub Apps, external services, and GitHub Actions work together to automate processes in your enterprise. * [Identity and access management fundamentals](/en/enterprise-server@3.22/admin/concepts/identity-and-access-management/identity-and-access-management-fundamentals) Administrators must decide how users will access the enterprise's resources on GitHub. * [Enterprise policies](/en/enterprise-server@3.22/admin/concepts/security-and-compliance/enterprise-policies) With enterprise policies, you can manage the policies for all the organizations owned by your enterprise. * [Audit log for an enterprise](/en/enterprise-server@3.22/admin/concepts/security-and-compliance/audit-log-for-an-enterprise) To support debugging and internal and external compliance, GitHub provides logs of audited user, organization, and repository events. * [Best practices for organizing work in your enterprise](/en/enterprise-server@3.22/admin/concepts/enterprise-best-practices/organize-work) Promote collaboration and manage resources at scale by following GitHub-recommended practices for managing organizations and teams. * [Using innersource in your enterprise](/en/enterprise-server@3.22/admin/concepts/enterprise-best-practices/use-innersource) Help dispersed teams to collaborate by setting up open source–style workflows in your enterprise, without compromising on security. * [Creating a README for an enterprise](/en/enterprise-server@3.22/admin/managing-your-enterprise-account/creating-a-readme-for-an-enterprise) You can create a README to tell your members what is happening in your enterprise. * [Configuring user display names for your enterprise](/en/enterprise-server@3.22/admin/managing-your-enterprise-account/configuring-user-display-names-for-your-enterprise) You can choose whether the profile name (first and last name) of your enterprise members appear alongside their username across GitHub. * [Installing GitHub Enterprise Server on AWS](/en/enterprise-server@3.22/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws) To install GitHub Enterprise Server on Amazon Web Services (AWS), you must launch an Amazon Elastic Compute Cloud (EC2) instance and create and attach a separate Amazon Elastic Block Store (EBS) data volume. * [Installing GitHub Enterprise Server on Azure](/en/enterprise-server@3.22/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure) To install GitHub Enterprise Server on Azure, you must deploy onto a memory-optimized instance that supports premium storage. * [Installing GitHub Enterprise Server on Google Cloud Platform](/en/enterprise-server@3.22/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform) To install GitHub Enterprise Server on Google Cloud Platform, you must deploy onto a supported machine type and use a persistent standard disk or a persistent SSD. * [Installing GitHub Enterprise Server on Hyper-V](/en/enterprise-server@3.22/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v) To install GitHub Enterprise Server on Hyper-V, you must deploy onto a machine running Windows Server 2008 through Windows Server 2022. * [Installing GitHub Enterprise Server on OpenStack KVM](/en/enterprise-server@3.22/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm) To install GitHub Enterprise Server on OpenStack KVM, you must have OpenStack access and download the GitHub Enterprise Server QCOW2 image. * [Installing GitHub Enterprise Server on VMware](/en/enterprise-server@3.22/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware) To install GitHub Enterprise Server on VMware, you must download the VMware vSphere client, and then download and deploy the GitHub Enterprise Server software. * [Setting up a staging instance](/en/enterprise-server@3.22/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance) You can set up a GitHub Enterprise Server instance in a separate, isolated environment, and use the instance to validate and test changes. * [Configuring applications](/en/enterprise-server@3.22/admin/configuring-settings/configuring-user-applications-for-your-enterprise/configuring-applications) You can configure internal application settings for GitHub.com. * [Configuring email for notifications](/en/enterprise-server@3.22/admin/configuring-settings/configuring-user-applications-for-your-enterprise/configuring-email-for-notifications) To make it easy for users to respond quickly to activity, you can configure GitHub.com to send email notifications for issue, pull request, and commit comments. * [Configuring GitHub Pages for your enterprise](/en/enterprise-server@3.22/admin/configuring-settings/configuring-user-applications-for-your-enterprise/configuring-github-pages-for-your-enterprise) You can enable or disable GitHub Pages for your enterprise and choose whether to make sites publicly accessible. * [Configuring rate limits](/en/enterprise-server@3.22/admin/configuring-settings/configuring-user-applications-for-your-enterprise/configuring-rate-limits) You can set rate limits for GitHub Enterprise Server using the Management Console. * [Best practices for configuring API rate limits](/en/enterprise-server@3.22/admin/configuring-settings/configuring-user-applications-for-your-enterprise/best-practices-for-configuring-api-rate-limits) A data-driven approach to API rate limits protects your GitHub Enterprise Server instance from excessive usage without disrupting critical integrations. * [Configuring web commit signing](/en/enterprise-server@3.22/admin/configuring-settings/configuring-user-applications-for-your-enterprise/configuring-web-commit-signing) You can enable auto-signing of commits made in the web interface of GitHub Enterprise Server. * [Configuring interactive maps](/en/enterprise-server@3.22/admin/configuring-settings/configuring-user-applications-for-your-enterprise/configuring-interactive-maps) You can enable the display of interactive maps in the web interface for GitHub.com. * [Managing GitHub Mobile for your enterprise](/en/enterprise-server@3.22/admin/configuring-settings/configuring-user-applications-for-your-enterprise/managing-github-mobile-for-your-enterprise) You can decide whether people can use GitHub Mobile to connect to GitHub.com. * [Verifying or approving a domain for your enterprise](/en/enterprise-server@3.22/admin/configuring-settings/configuring-user-applications-for-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise) You can verify your ownership of domains with GitHub to confirm the identity of organizations owned by your enterprise account. You can also approve domains where organization members can receive email notifications. * [Disabling persistent commit verification](/en/enterprise-server@3.22/admin/configuring-settings/configuring-user-applications-for-your-enterprise/disabling-persistent-commit-verification) You can disable persistent commit verification on GitHub Enterprise Server to reduce disk usage. * [Configuring TLS](/en/enterprise-server@3.22/admin/configuring-settings/hardening-security-for-your-enterprise/configuring-tls) You can configure Transport Layer Security (TLS) on GitHub.com so that you can use a certificate that is signed by a trusted certificate authority. * [Configuring TLS and SSH ciphers](/en/enterprise-server@3.22/admin/configuring-settings/hardening-security-for-your-enterprise/configuring-tls-and-ssh-ciphers) You can configure the cipher suites and cryptographic algorithms that GitHub Enterprise Server uses for TLS and SSH connections to meet specific compliance or security requirements. * [Troubleshooting TLS errors](/en/enterprise-server@3.22/admin/configuring-settings/hardening-security-for-your-enterprise/troubleshooting-tls-errors) If you run into TLS issues with your appliance, you can take actions to resolve them. * [Enabling private mode](/en/enterprise-server@3.22/admin/configuring-settings/hardening-security-for-your-enterprise/enabling-private-mode) In private mode, GitHub Enterprise Server requires every user to sign in to access the installation. * [Enabling subdomain isolation](/en/enterprise-server@3.22/admin/configuring-settings/hardening-security-for-your-enterprise/enabling-subdomain-isolation) You can set up subdomain isolation to securely separate user-supplied content from other portions of your GitHub Enterprise Server appliance. * [Configuring host keys for your instance](/en/enterprise-server@3.22/admin/configuring-settings/hardening-security-for-your-enterprise/configuring-host-keys-for-your-instance) You can increase the security of GitHub.com by configuring the algorithms that your instance uses to generate and advertise host keys for incoming SSH connections. * [Configuring SSH connections to your instance](/en/enterprise-server@3.22/admin/configuring-settings/hardening-security-for-your-enterprise/configuring-ssh-connections-to-your-instance) You can increase the security of GitHub.com by configuring the SSH algorithms that clients can use to establish a connection. * [Configuring the referrer policy for your enterprise](/en/enterprise-server@3.22/admin/configuring-settings/hardening-security-for-your-enterprise/configuring-the-referrer-policy-for-your-enterprise) You can increase the privacy of GitHub.com by configuring the policy for cross-origin requests. * [Configuring the IP address using the virtual machine console](/en/enterprise-server@3.22/admin/configuring-settings/configuring-network-settings/configuring-the-ip-address-using-the-virtual-machine-console) By default, GitHub Enterprise Server retrieves network settings via the dynamic host configuration protocol (DHCP). If your platform supports it, or if DHCP is unavailable, you can also configure the network settings using the virtual machine console. * [Configuring DNS nameservers](/en/enterprise-server@3.22/admin/configuring-settings/configuring-network-settings/configuring-dns-nameservers) GitHub Enterprise Server uses the dynamic host configuration protocol (DHCP) for DNS settings when DHCP leases provide nameservers. If nameservers are not provided by a dynamic host configuration protocol (DHCP) lease, or if you need to use specific DNS settings, you can specify the nameservers manually. * [Configuring the hostname for your instance](/en/enterprise-server@3.22/admin/configuring-settings/configuring-network-settings/configuring-the-hostname-for-your-instance) You can provide reliable access to GitHub.com by assigning a hostname that's accessible over your network. * [Changing the hostname for your instance](/en/enterprise-server@3.22/admin/configuring-settings/configuring-network-settings/changing-the-hostname-for-your-instance) If you want to change the hostname for an existing GitHub Enterprise Server instance, you must restore the settings and data to a new instance. * [Validating your domain settings](/en/enterprise-server@3.22/admin/configuring-settings/configuring-network-settings/validating-your-domain-settings) Ensure that your domain settings are properly configured before booting up GitHub.com for the first time. * [Configuring an outbound web proxy server](/en/enterprise-server@3.22/admin/configuring-settings/configuring-network-settings/configuring-an-outbound-web-proxy-server) A proxy server provides an additional level of security for GitHub.com. * [Configuring built-in firewall rules](/en/enterprise-server@3.22/admin/configuring-settings/configuring-network-settings/configuring-built-in-firewall-rules) You can view default firewall rules and customize rules for GitHub.com. * [Network ports](/en/enterprise-server@3.22/admin/configuring-settings/configuring-network-settings/network-ports) Open network ports selectively based on the network services you need to expose for administrators, end users, and email support. * [Using GitHub Enterprise Server with a load balancer](/en/enterprise-server@3.22/admin/configuring-settings/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer) Use a load balancer in front of a single GitHub Enterprise Server instance or a pair of instances in a High Availability configuration. * [Configuring time synchronization](/en/enterprise-server@3.22/admin/configuring-settings/configuring-network-settings/configuring-time-synchronization) GitHub Enterprise Server automatically synchronizes its clock by connecting to NTP servers. You can set the NTP servers that are used to synchronize the clock, or you can use the default NTP servers. * [About GitHub Connect](/en/enterprise-server@3.22/admin/configuring-settings/configuring-github-connect/about-github-connect) GitHub Connect enhances GitHub Enterprise Server by giving you access to data and workflows from GitHub Enterprise Cloud. * [Enabling GitHub Connect for GitHub.com](/en/enterprise-server@3.22/admin/configuring-settings/configuring-github-connect/enabling-github-connect-for-githubcom) Enable GitHub Connect to access additional features and workflows from GitHub.com on GitHub.com. * [Enabling GitHub Connect for GHE.com](/en/enterprise-server@3.22/admin/configuring-settings/configuring-github-connect/enabling-github-connect-for-ghecom) Enable GitHub Connect to share data between GHE.com and GitHub.com. * [Enabling automatic user license sync for your enterprise](/en/enterprise-server@3.22/admin/configuring-settings/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise) You can manage license usage across your GitHub Enterprise environments by automatically syncing user licenses from GitHub.com to GitHub Enterprise Cloud. * [Enabling Dependabot for your enterprise](/en/enterprise-server@3.22/admin/configuring-settings/configuring-github-connect/enabling-dependabot-for-your-enterprise) You can allow users to find and fix vulnerabilities in code dependencies by setting up Dependabot alerts and Dependabot updates. * [Enabling Server Statistics for your enterprise](/en/enterprise-server@3.22/admin/configuring-settings/configuring-github-connect/enabling-server-statistics-for-your-enterprise) You can analyze your own aggregate data from GitHub Enterprise Server and help us improve GitHub products by enabling Server Statistics. * [Enabling unified search for your enterprise](/en/enterprise-server@3.22/admin/configuring-settings/configuring-github-connect/enabling-unified-search-for-your-enterprise) You can allow users to include repositories on GitHub Enterprise Cloud in their search results when searching from GitHub.com. * [Enabling unified contributions for your enterprise](/en/enterprise-server@3.22/admin/configuring-settings/configuring-github-connect/enabling-unified-contributions-for-your-enterprise) You can allow users to include anonymized contribution counts for their work on GitHub.com in their contribution graphs on GitHub Enterprise Cloud. * [Disabling GitHub Connect](/en/enterprise-server@3.22/admin/configuring-settings/configuring-github-connect/disabling-github-connect) You can disable GitHub Connect to stop the connection from GitHub.com to GitHub Enterprise Cloud. * [About the Management Console](/en/enterprise-server@3.22/admin/administering-your-instance/administering-your-instance-from-the-web-ui/about-the-management-console) From the Management Console, you can initialize, configure, and monitor GitHub.com. * [Managing access to the Management Console](/en/enterprise-server@3.22/admin/administering-your-instance/administering-your-instance-from-the-web-ui/managing-access-to-the-management-console) You can increase the security of GitHub.com by creating or deleting Management Console users. As the root site administrator, you can access the Management Console as well as configure Management Console authentication rate limits. * [Accessing the Management Console](/en/enterprise-server@3.22/admin/administering-your-instance/administering-your-instance-from-the-web-ui/accessing-the-management-console) You can access the Management Console as the root site administrator or a Management Console user. * [Troubleshooting access to the Management Console](/en/enterprise-server@3.22/admin/administering-your-instance/administering-your-instance-from-the-web-ui/troubleshooting-access-to-the-management-console) You can troubleshoot access problems for the Management Console. * [Managing search indices for your instance](/en/enterprise-server@3.22/admin/administering-your-instance/administering-your-instance-from-the-web-ui/managing-search-indices-for-your-instance) GitHub Enterprise Server uses Elasticsearch to power search features, and provides tools for managing search and index behavior. * [Accessing the administrative shell (SSH)](/en/enterprise-server@3.22/admin/administering-your-instance/administering-your-instance-from-the-command-line/accessing-the-administrative-shell-ssh) SSH access allows you to run the GitHub Enterprise Server command line utilities to troubleshoot, run backups, and configure replication. * [Administering your instance using the GitHub CLI](/en/enterprise-server@3.22/admin/administering-your-instance/administering-your-instance-from-the-command-line/administering-your-instance-using-the-github-cli) You can administer your GitHub Enterprise Server instance using the GitHub CLI extension for GHES Manage API. * [Command-line utilities](/en/enterprise-server@3.22/admin/administering-your-instance/administering-your-instance-from-the-command-line/command-line-utilities) GitHub Enterprise Server includes a variety of utilities to help resolve particular problems or perform specific tasks. * [Enabling and scheduling maintenance mode](/en/enterprise-server@3.22/admin/administering-your-instance/configuring-maintenance-mode/enabling-and-scheduling-maintenance-mode) Some standard maintenance procedures, such as upgrading GitHub.com or restoring backups, require the instance to be taken offline for normal use. * [About SAML for enterprise IAM](/en/enterprise-server@3.22/admin/managing-iam/understanding-iam-for-enterprises/about-saml-for-enterprise-iam) You can use SAML single sign-on (SSO) to centrally manage access . * [Changing authentication methods](/en/enterprise-server@3.22/admin/managing-iam/understanding-iam-for-enterprises/changing-authentication-methods) You can change the way GitHub Enterprise Server authenticates with your existing accounts at any time. * [Allowing built-in authentication for users outside your provider](/en/enterprise-server@3.22/admin/managing-iam/understanding-iam-for-enterprises/allowing-built-in-authentication-for-users-outside-your-provider) You can configure fallback authentication to allow built-in authentication for people who don't have an account on your CAS, LDAP, or SAML authentication provider. * [Troubleshooting identity and access management for your enterprise](/en/enterprise-server@3.22/admin/managing-iam/understanding-iam-for-enterprises/troubleshooting-identity-and-access-management-for-your-enterprise) Review common issues and solutions for identity and access management for your enterprise. * [SAML configuration reference](/en/enterprise-server@3.22/admin/managing-iam/iam-configuration-reference/saml-configuration-reference) You can see SAML metadata for , and you can learn more about available SAML attributes and response requirements. * [Username considerations for external authentication](/en/enterprise-server@3.22/admin/managing-iam/iam-configuration-reference/username-considerations-for-external-authentication) When you use , GitHub follows certain rules to determine the username for each user account . * [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. * [Using CAS](/en/enterprise-server@3.22/admin/managing-iam/using-cas-for-enterprise-iam/using-cas) If you use Central Authentication Service (CAS) to centralize access to multiple web applications, you can integrate GitHub Enterprise Server by configuring CAS authentication for your instance. * [Using LDAP](/en/enterprise-server@3.22/admin/managing-iam/using-ldap-for-enterprise-iam/using-ldap) If you use Lightweight Directory Access Protocol (LDAP) to centralize access across applications, you can integrate GitHub Enterprise Server by configuring LDAP authentication for your instance. * [Configuring SAML single sign-on for your enterprise](/en/enterprise-server@3.22/admin/managing-iam/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise) You can control and secure access to by SAML single sign-on (SSO) through your identity provider (IdP). * [Enabling encrypted assertions](/en/enterprise-server@3.22/admin/managing-iam/using-saml-for-enterprise-iam/enabling-encrypted-assertions) You can improve GitHub.com's security with SAML single sign-on (SSO) by encrypting the messages that your SAML identity provider (IdP) sends. * [Updating a user's SAML NameID](/en/enterprise-server@3.22/admin/managing-iam/using-saml-for-enterprise-iam/updating-a-users-saml-nameid) When an account's `NameID` changes on your identity provider (IdP) and the person can no longer sign into GitHub.com, you must update the `NameID` mapping on GitHub.com. * [Troubleshooting SAML authentication](/en/enterprise-server@3.22/admin/managing-iam/using-saml-for-enterprise-iam/troubleshooting-saml-authentication) If you use SAML single sign-on (SSO) and people are unable to authenticate to access GitHub, you can troubleshoot the problem. * [About user provisioning with SCIM on GitHub Enterprise Server](/en/enterprise-server@3.22/admin/managing-iam/provisioning-user-accounts-with-scim/user-provisioning-with-scim-on-ghes) Learn about managing the lifecycle of user accounts with SCIM on GitHub.com. * [Configuring SCIM provisioning to manage users](/en/enterprise-server@3.22/admin/managing-iam/provisioning-user-accounts-with-scim/configuring-scim-provisioning-for-users) You can manage the lifecycle of your enterprise's user accounts from your identity provider (IdP) using System for Cross-domain Identity Management (SCIM). * [Migrating from LDAP to SAML with SCIM](/en/enterprise-server@3.22/admin/managing-iam/provisioning-user-accounts-with-scim/migrating-from-ldap-to-saml-with-scim) Learn how to migrate your GitHub Enterprise Server instance from LDAP authentication to SAML single sign-on with SCIM provisioning for centralized user management. * [Configuring authentication and provisioning with Entra ID](/en/enterprise-server@3.22/admin/managing-iam/provisioning-user-accounts-with-scim/configuring-authentication-and-provisioning-with-entra-id) You can use a tenant in Microsoft Entra ID (previously known as Azure AD) as an identity provider (IdP) to centrally manage authentication and user provisioning for GitHub.com. * [Configuring authentication and provisioning with PingFederate](/en/enterprise-server@3.22/admin/managing-iam/provisioning-user-accounts-with-scim/configuring-authentication-and-provisioning-with-pingfederate) Set up PingFederate as an identity provider (IdP) for Enterprise Managed Users on GitHub.com or GHE.com. * [Configuring authentication and provisioning with Okta](/en/enterprise-server@3.22/admin/managing-iam/provisioning-user-accounts-with-scim/configuring-scim-provisioning-with-okta) Learn how to configure Okta to communicate with your enterprise. * [Disabling SCIM provisioning for users](/en/enterprise-server@3.22/admin/managing-iam/provisioning-user-accounts-with-scim/disabling-scim-provisioning-for-users) You can disable SCIM provisioning for your enterprise's user accounts. * [Provisioning users and groups with SCIM using the REST API](/en/enterprise-server@3.22/admin/managing-iam/provisioning-user-accounts-with-scim/provisioning-users-and-groups-with-scim-using-the-rest-api) Manage the lifecycle of user accounts from your identity provider using GitHub's REST API for System for Cross-domain Identity Management (SCIM). * [Managing team memberships with identity provider groups](/en/enterprise-server@3.22/admin/managing-iam/provisioning-user-accounts-with-scim/managing-team-memberships-with-identity-provider-groups) Connect IdP groups with teams on GitHub to manage team and organization membership through your identity provider. * [Deprovisioning and reinstating users with SCIM](/en/enterprise-server@3.22/admin/managing-iam/provisioning-user-accounts-with-scim/deprovisioning-and-reinstating-users) Learn details about deprovisioning or reinstating users. * [Troubleshooting team membership with identity provider groups](/en/enterprise-server@3.22/admin/managing-iam/provisioning-user-accounts-with-scim/troubleshooting-team-membership-with-identity-provider-groups) If you manage team membership using groups on your identity provider (IdP), but team membership is not in sync, you can troubleshoot the problem. * [Customizing user messages for your enterprise](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/communicating-information-to-users-in-your-enterprise/customizing-user-messages-for-your-enterprise) You can create custom messages that users will see on GitHub. * [Configuring custom footers](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/communicating-information-to-users-in-your-enterprise/configuring-custom-footers) You can give users easy access to enterprise-specific links by adding custom footers. * [Best practices for user security](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/best-practices-for-user-security) Outside of instance-level security measures (SSL, subdomain isolation, configuring a firewall) that a site administrator can implement, there are steps your users can take to help protect your enterprise. * [Creating enterprise teams](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/create-enterprise-teams) Organize users into teams to simplify license management. * [Inviting people to manage your enterprise](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise) You can add and remove enterprise owners for your enterprise account. * [About reserved usernames for GitHub Enterprise Server](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/about-reserved-usernames-for-github-enterprise-server) Certain words are reserved for internal use and cannot be used as usernames. * [Promoting or demoting a site administrator](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator) Site administrators can promote any normal user account to a site administrator, as well as demote other site administrators to regular users. * [Viewing people in your enterprise](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/viewing-people-in-your-enterprise) To audit access to enterprise-owned resources or user license usage, enterprise owners can view every administrator and member of the enterprise. * [Viewing and managing a user's SAML access to your enterprise](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise) You can view and revoke an enterprise member's active SAML sessions. * [Auditing users across your enterprise](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/auditing-users-across-your-enterprise) The audit log dashboard shows site administrators the actions performed by all users and organizations across your enterprise within the last 180 days. The audit log includes details such as who performed the action, what the action was, and when the action was performed. * [Impersonating a user](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/impersonating-a-user) You can impersonate users and perform actions on their behalf, for troubleshooting, unblocking, and other legitimate reasons. * [Managing dormant users](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/managing-dormant-users) By default, a user account is considered to be dormant if it has not been active for 30 days. You can configure the length of time a user must be inactive to be considered dormant. * [Suspending and unsuspending users](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/suspending-and-unsuspending-users) If a user leaves or moves to a different part of the company, you should remove or modify their ability to access GitHub.com. * [Deleting users from your instance](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/deleting-users-from-your-instance) You can delete a user's account to permanently remove their data from GitHub.com. * [Placing a legal hold on a user or organization](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/placing-a-legal-hold-on-a-user-or-organization) You can place a legal hold on a user or organization to ensure that repositories they own cannot be permanently removed from your enterprise. * [Auditing SSH keys](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/auditing-ssh-keys) Site administrators can initiate an instance-wide audit of SSH keys. * [Rebuilding contributions data](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/rebuilding-contributions-data) You may need to rebuild contributions data to link existing commits to a user account. * [Configuring visibility for organization membership](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/configuring-visibility-for-organization-membership) 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. * [Preventing users from creating organizations](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations) You can prevent users from creating organizations in your enterprise. * [Requiring two-factor authentication for an organization](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization) 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. * [Custom properties](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/custom-properties) Custom properties allow you to add structured metadata to repositories and organizations, enabling better organization, governance, and automation across your GitHub environment. * [Managing custom properties for organizations](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/managing-custom-properties-for-organizations) With custom properties, you can add metadata to organizations in your enterprise and use that metadata to target repositories with rulesets. * [Managing your role in an organization owned by your enterprise](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise) You can manage your membership in any organization owned by your enterprise and change your role within the organization. * [Restoring a deleted organization](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/restoring-a-deleted-organization) You can partially restore an organization that was previously deleted on GitHub.com. * [Managing projects using Jira](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/managing-projects-using-jira) You can integrate Jira with GitHub Enterprise Server for project management. * [Managing custom properties for repositories in your enterprise](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-repositories-in-your-enterprise/managing-custom-properties-for-repositories-in-your-enterprise) Create custom properties to give organizations a consistent way to categorize repositories. * [Configuring Git Large File Storage for your enterprise](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise) Git Large File Storage (Git LFS) is an open source extension to Git that allows you to work with large files the same way as other text files. * [Disabling Git SSH access on your enterprise](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise) You can prevent people from using Git over SSH for certain or all repositories on your enterprise. * [Locking a repository](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-repositories-in-your-enterprise/locking-a-repository) You can prevent changes to a repository's code and other resources, such as issues and pull requests, by locking the repository. * [Restoring a deleted repository](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-repositories-in-your-enterprise/restoring-a-deleted-repository) You can restore deleted repositories to recover their contents. * [Troubleshooting service hooks](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-repositories-in-your-enterprise/troubleshooting-service-hooks) If payloads aren't being delivered, check for these common problems. * [Identifying the roles required by your enterprise](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-roles-in-your-enterprise/identify-role-requirements) Plan which roles your teams need to stay productive and secure. * [Creating custom roles in an enterprise](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-roles-in-your-enterprise/create-custom-roles) Create roles with fine-grained permissions for consistent access to settings and resources. * [Assigning roles to people in an enterprise](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-roles-in-your-enterprise/assign-roles) Govern what people can do in your enterprise by assigning roles to users and teams. * [Abilities of roles in an enterprise](/en/enterprise-server@3.22/admin/managing-accounts-and-repositories/managing-roles-in-your-enterprise/abilities-of-roles) Find the right role to grant access to your enterprise's settings and data. * [Overview of the upgrade process](/en/enterprise-server@3.22/admin/upgrading-your-instance/preparing-to-upgrade/overview-of-the-upgrade-process) Learn the recommendations and requirements for upgrading GitHub Enterprise Server, so you can plan and test your upgrade strategy. * [Upgrade requirements](/en/enterprise-server@3.22/admin/upgrading-your-instance/preparing-to-upgrade/upgrade-requirements) Before upgrading GitHub Enterprise Server, review these recommendations and requirements to plan your upgrade strategy. * [Enabling automatic update checks](/en/enterprise-server@3.22/admin/upgrading-your-instance/preparing-to-upgrade/enabling-automatic-update-checks) You can enable automatic update checks so that GitHub.com checks for and downloads the latest GitHub Enterprise Server release. * [Taking a snapshot](/en/enterprise-server@3.22/admin/upgrading-your-instance/preparing-to-upgrade/taking-a-snapshot) To save your GitHub Enterprise Server data before upgrading, take a virtual machine snapshot. * [Check system capacity before upgrading](/en/enterprise-server@3.22/admin/upgrading-your-instance/preparing-to-upgrade/check-system-capacity-before-upgrading) Before upgrading GitHub Enterprise Server, you should perform these capacity checks and take the recommended steps. * [Upgrading with a hotpatch](/en/enterprise-server@3.22/admin/upgrading-your-instance/performing-an-upgrade/upgrading-with-a-hotpatch) You can use a hotpatch package to upgrade GitHub Enterprise Server to a newer patch release within a feature series. * [Upgrading with an upgrade package](/en/enterprise-server@3.22/admin/upgrading-your-instance/performing-an-upgrade/upgrading-with-an-upgrade-package) Learn how to use an upgrade package to upgrade GitHub Enterprise Server to a newer feature release. * [Migrating from GitHub Enterprise 11.10.x to 2.1.23](/en/enterprise-server@3.22/admin/upgrading-your-instance/performing-an-upgrade/migrating-from-github-enterprise-1110x-to-2123) To migrate from GitHub Enterprise 11.10.x to 2.1.23, you'll need to set up a new appliance instance and migrate data from the previous instance. * [Restoring from a failed upgrade](/en/enterprise-server@3.22/admin/upgrading-your-instance/troubleshooting-upgrades/restoring-from-a-failed-upgrade) Learn how to roll back from a failed upgrade. * [Known issues with upgrades to your instance](/en/enterprise-server@3.22/admin/upgrading-your-instance/troubleshooting-upgrades/known-issues-with-upgrades-to-your-instance) See an overview of workarounds for issues that impact the upgrade process for GitHub Enterprise Server, or impact your instance after you complete an upgrade. * [Rotating the signing key for upgrade packages](/en/enterprise-server@3.22/admin/upgrading-your-instance/troubleshooting-upgrades/rotating-the-signing-key-for-upgrade-packages) Learn how to rotate the GPG public key on GitHub Enterprise Server when GitHub updates the key used to sign upgrade packages. * [About the backup service for GitHub Enterprise Server](/en/enterprise-server@3.22/admin/backing-up-and-restoring-your-instance/about-the-backup-service-for-github-enterprise-server) Learn what the built-in backup service offers and how it differs from a High Availability replica. * [Understanding the backup service](/en/enterprise-server@3.22/admin/backing-up-and-restoring-your-instance/understanding-the-backup-service) Answers to common questions about using the backup service with GitHub Enterprise Server. * [Configuring the backup service](/en/enterprise-server@3.22/admin/backing-up-and-restoring-your-instance/configuring-the-backup-service) Enable and configure the built-in backup service in the Management Console, and optionally migrate legacy settings. * [Creating and monitoring backups](/en/enterprise-server@3.22/admin/backing-up-and-restoring-your-instance/creating-and-monitoring-backups) Run manual backups, understand backup types, and monitor backup activity using the Management Console or command line. * [Restoring from a backup](/en/enterprise-server@3.22/admin/backing-up-and-restoring-your-instance/restoring-from-a-backup) Restore a GitHub Enterprise Server instance using a previously created backup snapshot. * [Configuring remote archives for backups](/en/enterprise-server@3.22/admin/backing-up-and-restoring-your-instance/configuring-remote-archives-for-backups) Enable a remote archive for backups through SSH. * [Backup from replica in high availability](/en/enterprise-server@3.22/admin/backing-up-and-restoring-your-instance/backup-from-replica-in-high-availability) Enable backup from a high availability replica node. * [Backup in clustering mode](/en/enterprise-server@3.22/admin/backing-up-and-restoring-your-instance/backup-in-clustering-mode) Enable backup from a node in cluster. * [Restoring with GitHub Actions enabled](/en/enterprise-server@3.22/admin/backing-up-and-restoring-your-instance/restoring-with-github-actions-enabled) Learn how to prepare for and restore backups when GitHub Actions is enabled with external blob storage. * [Backup service settings reference](/en/enterprise-server@3.22/admin/backing-up-and-restoring-your-instance/backup-service-settings-reference) Reference for all configurable options available in the Backup Service section of the Management Console. * [Understanding the snapshot file structure](/en/enterprise-server@3.22/admin/backing-up-and-restoring-your-instance/understanding-the-snapshot-file-structure) Understand the structure and contents of backup snapshot directories, including what is stored and how hard links are used. * [Enforcing repository management policies in your enterprise](/en/enterprise-server@3.22/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise) You can enforce policies for repository management within your enterprise's organizations, or allow policies to be set in each organization. * [Enforcing policies for projects in your enterprise](/en/enterprise-server@3.22/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-projects-in-your-enterprise) You can enforce policies for projects within your enterprise's organizations, or allow policies to be set in each organization. * [Restricting email notifications for your enterprise](/en/enterprise-server@3.22/admin/enforcing-policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise) You can prevent your enterprise's information from leaking into personal email accounts by restricting the domains where members can receive email notifications about activity in organizations owned by your enterprise. * [Enforcing policies for security settings in your enterprise](/en/enterprise-server@3.22/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise) You can enforce policies to manage security settings in your enterprise's organizations, or allow policies to be set in each organization. * [Enforcing policies for GitHub Actions in your enterprise](/en/enterprise-server@3.22/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise) You can enforce policies to manage how GitHub Actions can be used within your enterprise. * [Enforcing policies for code security and analysis for your enterprise](/en/enterprise-server@3.22/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise) You can enforce policies to manage the use of code security and analysis features within your enterprise's organizations. * [Enforcing policies for personal access tokens in your enterprise](/en/enterprise-server@3.22/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise) Enterprise owners can control access to resources by applying policies to personal access tokens * [About pre-receive hooks](/en/enterprise-server@3.22/admin/enforcing-policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks) *Pre-receive hooks* are scripts that run on the GitHub Enterprise Server appliance that you can use to implement quality checks. * [Creating a pre-receive hook environment](/en/enterprise-server@3.22/admin/enforcing-policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment) To execute pre-receive hooks, use either the default pre-receive environment, or create a custom environment. * [Creating a pre-receive hook script](/en/enterprise-server@3.22/admin/enforcing-policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script) Use pre-receive hook scripts to create requirements for accepting or rejecting a push based on the contents. * [Managing pre-receive hooks on your instance](/en/enterprise-server@3.22/admin/enforcing-policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-your-instance) Configure how people will use pre-receive hooks on GitHub.com. * [Accessing the audit log for your enterprise](/en/enterprise-server@3.22/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise) You can view aggregated actions from all of the organizations owned by an enterprise account in the enterprise's audit log. * [Configuring the audit log for your enterprise](/en/enterprise-server@3.22/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise) You can configure settings for your enterprise's audit log. * [Searching the audit log for your enterprise](/en/enterprise-server@3.22/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise) You can search an extensive list of audited actions in your enterprise. * [Identifying audit log events performed by an access token](/en/enterprise-server@3.22/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/identifying-audit-log-events-performed-by-an-access-token) You can identify the actions performed by a specific token in your enterprise. * [Streaming the audit log for your enterprise](/en/enterprise-server@3.22/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise) Learn how to stream audit and Git events data from GitHub to an external data management system. * [Using the audit log API for your enterprise](/en/enterprise-server@3.22/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise) Learn how to programmatically retrieve enterprise events with the REST API. * [Audit log events for your enterprise](/en/enterprise-server@3.22/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise) Review the events recorded in an enterprise's audit log. * [Accessing reports for your instance](/en/enterprise-server@3.22/admin/monitoring-activity-in-your-enterprise/exploring-user-activity-in-your-enterprise/accessing-reports-for-your-instance) You can download reports with information about the users, organizations, and repositories on GitHub.com. * [Viewing push logs](/en/enterprise-server@3.22/admin/monitoring-activity-in-your-enterprise/exploring-user-activity-in-your-enterprise/viewing-push-logs) Site administrators can view a list of Git push operations for any repository on the enterprise. * [Log forwarding](/en/enterprise-server@3.22/admin/monitoring-activity-in-your-enterprise/exploring-user-activity-in-your-enterprise/log-forwarding) GitHub Enterprise Server uses `syslog-ng` to forward system and application logs to the server you specify. * [Managing global webhooks](/en/enterprise-server@3.22/admin/monitoring-activity-in-your-enterprise/exploring-user-activity-in-your-enterprise/managing-global-webhooks) You can configure global webhooks to notify external web servers when events occur within your enterprise. * [About Server Statistics](/en/enterprise-server@3.22/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics) You can use Server Statistics to analyze your own aggregate data from GitHub Enterprise Server, and help us improve GitHub products. * [Exporting Server Statistics](/en/enterprise-server@3.22/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics) You can use your own tools to analyze your GitHub Enterprise Server usage over time by downloading your Server Statistics metrics in a CSV or JSON file. * [Requesting Server Statistics using the REST API](/en/enterprise-server@3.22/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api) You can use your own tools to analyze your GitHub Enterprise Server usage over time by requesting the Server Statistics metrics collected using the REST API. * [About monitoring your instance](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/monitoring-your-instance/about-monitoring-your-instance) You can configure monitoring and alerting so that you're aware of potential issues before they negatively impact application performance or availability. * [About the monitor dashboards](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/monitoring-your-instance/about-the-monitor-dashboards) View historical data for details like CPU and storage usage, application and authentication response times, and general system health. * [Analyzing Git traffic on your GitHub Enterprise Server instance](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/monitoring-your-instance/analyze-git-traffic) Use Governor to identify Git traffic patterns that are driving load on your instance, so you can troubleshoot slow Git operations and reduce performance impact. * [Recommended alert thresholds](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/monitoring-your-instance/recommended-alert-thresholds) You can configure an alert to notify you of system resource issues before they affect your GitHub Enterprise Server appliance's performance. * [About OpenTelemetry metrics](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/monitoring-your-instance/opentelemetry-metrics/about-opentelemetry-metrics) OpenTelemetry metrics provide a comprehensive monitoring solution for GitHub Enterprise Server instances, offering enhanced observability and management capabilities. * [Configuring OpenTelemetry for your instance](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/monitoring-your-instance/opentelemetry-metrics/configuring-opentelemetry-for-your-instance) Learn how to configure OpenTelemetry metrics collection on your GitHub Enterprise Server instance for enhanced monitoring and observability. * [Advanced dashboards of OpenTelemetry metrics](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/monitoring-your-instance/opentelemetry-metrics/advanced-dashboards) After enabling OpenTelemetry metrics collection on your GitHub Enterprise Server instance, you have access to additional dashboards with enhanced visualization and monitoring capabilities. * [Using Grafana to analyze OpenTelemetry metrics](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/monitoring-your-instance/opentelemetry-metrics/using-grafana-to-analyze-opentelemetry-metrics) Monitor the health and performance of your instance using dashboards and metrics provided by the OpenTelemetry metrics stack. * [Setting up external monitoring with OpenTelemetry](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/monitoring-your-instance/opentelemetry-metrics/setting-up-external-monitoring-with-opentelemetry) Configure external monitoring systems to collect and analyze OpenTelemetry metrics from your GitHub Enterprise Server instance. * [About Collectd metrics](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/monitoring-your-instance/collectd-metrics/about-collectd-metrics) Collectd metrics provide a legacy monitoring solution for GitHub Enterprise Server instances that is supported alongside a public preview of OpenTelemetry metrics. * [Setting up external monitoring with collectd](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/monitoring-your-instance/collectd-metrics/setting-up-external-monitoring-with-collectd) Configure external monitoring systems to collect and analyze collectd metrics from your GitHub Enterprise Server instance. * [collectd metrics for GitHub Enterprise Server](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/monitoring-your-instance/collectd-metrics/collectd-metrics-for-github-enterprise-server) You can review the metrics that `collectd` gathers for GitHub.com. * [Exporting and scraping Prometheus metrics](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/monitoring-your-instance/collectd-metrics/exporting-and-scraping-prometheus-metrics) GitHub Enterprise Server provides Prometheus-compatible metrics by transforming `collectd` data. These metrics can be scraped from a dedicated endpoint, allowing integration with observability and monitoring tools for performance insights. * [Monitoring using SNMP](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/monitoring-your-instance/monitoring-using-snmp) GitHub Enterprise provides data on disk usage, CPU utilization, memory usage, and more over SNMP. * [About system logs](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/monitoring-your-instance/about-system-logs) To help administrators understand activity and errors, GitHub Enterprise Server stores system logs. * [About support bundles for GitHub Enterprise Server](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/monitoring-your-instance/about-support-bundles) When something goes wrong on your GitHub Enterprise Server instance, a support bundle gives GitHub Support the diagnostic data they need to help you resolve the issue quickly. * [Troubleshooting resource allocation problems](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/monitoring-your-instance/troubleshooting-resource-allocation-problems) Troubleshooting common resource allocation issues that may occur on your GitHub Enterprise Server appliance. * [Generating a Health Check for your enterprise](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/monitoring-your-instance/generating-a-health-check-for-your-enterprise) You can gain insight into the general health and Git and API requests of GitHub.com by generating a Health Check. * [Increasing storage capacity](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity) You can increase or change the amount of storage available for Git repositories, databases, search indexes, and other persistent application data. * [Increasing CPU or memory resources](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources) You can increase the CPU or memory resources for the virtual machine (VM) that runs GitHub.com. * [Using generation 2 virtual machines](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/updating-the-virtual-machine-and-physical-resources/using-generation-2-virtual-machines) New installs of GitHub Enterprise Server 3.14 or later can use generation 2 virtual machines. * [Changing your platform](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/updating-the-virtual-machine-and-physical-resources/changing-your-platform) How to change the platform that runs GitHub.com * [About clustering](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/configuring-clustering/about-clustering) The cluster topology for GitHub Enterprise Server is designed to support tens of thousands of users where other topologies would experience resource exhaustion. In a cluster, the instance's services scale horizontally across multiple nodes. * [Differences between clustering and high availability (HA)](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/configuring-clustering/differences-between-clustering-and-high-availability-ha) Learn about the differences between deployment topologies for the virtual machines (VMs) that comprise a GitHub Enterprise Server instance. * [About cluster nodes](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/configuring-clustering/about-cluster-nodes) In a GitHub Enterprise Server cluster, nodes are individual virtual machines (VMs) running the GitHub Enterprise Server software that comprise the instance. Each node runs a set of services. * [Cluster network configuration](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/configuring-clustering/cluster-network-configuration) A GitHub Enterprise Server cluster requires proper DNS name resolution, load balancing, and communication between nodes. * [Initializing the cluster](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/configuring-clustering/initializing-the-cluster) A GitHub Enterprise Server cluster must be set up with a license and initialized using the administrative shell (SSH). * [Deferring database seeding](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/configuring-clustering/deferring-database-seeding) You can speed up the process of adding a new MySQL replica node to your cluster by opting to defer database seeding. * [Upgrading a cluster](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/configuring-clustering/upgrading-a-cluster) To upgrade a GitHub Enterprise Server cluster to the latest release, use the administrative shell (SSH). * [Monitoring the health of your cluster](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/configuring-clustering/monitoring-the-health-of-your-cluster) To ensure the performance and redundancy of a GitHub Enterprise Server cluster, you can monitor the cluster's health. * [Monitoring the health of your cluster nodes with Node Eligibility Service](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/configuring-clustering/monitoring-the-health-of-your-cluster-nodes-with-node-eligibility-service) You can monitor when nodes in a GitHub Enterprise Server cluster have been offline long enough to cause issues by using Node Eligibility Service. * [Rebalancing cluster workloads](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/configuring-clustering/rebalancing-cluster-workloads) You can force your GitHub Enterprise Server cluster to evenly distribute job allocations for workloads on the cluster's nodes. * [Replacing a cluster node](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/configuring-clustering/replacing-a-cluster-node) Replace a functional or failed node in a GitHub Enterprise Server cluster while preserving the services that the node provides. * [Configuring high availability replication for a cluster](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/configuring-clustering/configuring-high-availability-replication-for-a-cluster) You can configure a replica of your entire GitHub Enterprise Server cluster in a separate datacenter, allowing your cluster to fail over to redundant nodes. * [Initiating a failover to your replica cluster](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/configuring-clustering/initiating-a-failover-to-your-replica-cluster) If your GitHub Enterprise Server cluster fails, you can fail over to the replica. * [About high availability configuration](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/configuring-high-availability/about-high-availability-configuration) In a high availability configuration, a fully redundant secondary GitHub Enterprise Server appliance is kept in sync with the primary appliance through replication of all major datastores. * [Configuring Elasticsearch Cross-Cluster Replication for high availability](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/configuring-high-availability/elasticsearch-cross-cluster-replication) You can make search more resilient during maintenance, failovers, and upgrades on a high availability deployment by enabling Elasticsearch Cross-Cluster Replication (CCR). * [Answers to common questions about high availability replicas](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/configuring-high-availability/answers-to-common-questions-about-high-availability-replicas) Find information about high availability replica types, communication patterns, maintenance operations, and how to choose the right replica for your deployment. * [Creating a high availability replica](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/configuring-high-availability/creating-a-high-availability-replica) In an active/passive configuration, the replica appliance is a redundant copy of the primary appliance. If the primary appliance fails, high availability mode allows the replica to act as the primary appliance, allowing minimal service disruption. * [Monitoring a high-availability configuration](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/configuring-high-availability/monitoring-a-high-availability-configuration) After configuration of high availability for GitHub.com, you can monitor the status of data replication among to your instance's replica nodes. * [Initiating a failover to your replica appliance](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/configuring-high-availability/initiating-a-failover-to-your-replica-appliance) You can failover to a GitHub Enterprise Server replica appliance using the command line for maintenance and testing, or if the primary appliance fails. * [Recovering a high availability configuration](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/configuring-high-availability/recovering-a-high-availability-configuration) After failing over to a GitHub Enterprise Server appliance, you should regain redundancy as soon as possible rather than rely on a single appliance. * [Removing a high availability replica](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/configuring-high-availability/removing-a-high-availability-replica) You can stop replication to a GitHub Enterprise Server replica temporarily, or permanently remove replication. * [About geo-replication](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/configuring-high-availability/about-geo-replication) Geo-replication on GitHub Enterprise Server uses multiple active replicas to fulfill requests from geographically distributed data centers. * [About repository caching](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/caching-repositories/about-repository-caching) You can increase the performance of Git read operations for distributed teams and CI farms with repository caching. * [Configuring a repository cache](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/caching-repositories/configuring-a-repository-cache) You can configure a repository cache for GitHub Enterprise Server by creating a new instance, connecting the repository cache to your primary instance, and configuring replication of repository networks to the repository cache. * [Configuring multiple data disks](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/multiple-data-disks/configuring-multiple-data-disks) You can configure additional data disks and use them to host data of different services. * [Adding nodes to a high availability configuration](/en/enterprise-server@3.22/admin/monitoring-and-managing-your-instance/additional-nodes/configuring-additional-nodes) Add nodes to the primary high availability (HA) datacenter. This is intended to offload CPU-intensive tasks from the primary node, allowing for horizontal scaling of the GitHub Enterprise Server instance. * [Creating GitHub Apps for your enterprise](/en/enterprise-server@3.22/admin/managing-github-apps-for-your-enterprise/creating-github-apps-for-your-enterprise) Learn how to create a GitHub App for your enterprise. * [Adding and removing GitHub App managers in your enterprise](/en/enterprise-server@3.22/admin/managing-github-apps-for-your-enterprise/adding-and-removing-github-app-managers-in-your-enterprise) Enterprise owners can grant or revoke access for a user to manage GitHub Apps owned by the enterprise. * [About GitHub Actions for enterprises](/en/enterprise-server@3.22/admin/managing-github-actions-for-your-enterprise/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises) GitHub Actions can improve developer productivity by automating your enterprise's software development cycle. * [Introducing GitHub Actions to your enterprise](/en/enterprise-server@3.22/admin/managing-github-actions-for-your-enterprise/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise) You can plan how to roll out GitHub Actions in your enterprise. * [Migrating your enterprise to GitHub Actions](/en/enterprise-server@3.22/admin/managing-github-actions-for-your-enterprise/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions) Learn how to plan a migration to GitHub Actions for your enterprise from another provider. * [Getting started with GitHub Actions for GitHub Enterprise Server](/en/enterprise-server@3.22/admin/managing-github-actions-for-your-enterprise/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server) Learn about enabling and configuring GitHub Actions on GitHub Enterprise Server for the first time. * [Getting started with self-hosted runners for your enterprise](/en/enterprise-server@3.22/admin/managing-github-actions-for-your-enterprise/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise) You can configure a runner machine for your enterprise so your developers can start automating workflows with GitHub Actions. * [Enabling GitHub Actions with Azure Blob storage](/en/enterprise-server@3.22/admin/managing-github-actions-for-your-enterprise/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage) You can enable GitHub Actions on GitHub Enterprise Server and use Azure Blob storage to store data generated by workflow runs. * [Enabling GitHub Actions with Amazon S3 storage](/en/enterprise-server@3.22/admin/managing-github-actions-for-your-enterprise/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage) You can enable GitHub Actions on GitHub Enterprise Server and use Amazon S3 storage to store data generated by workflow runs. * [Enabling GitHub Actions with Google Cloud Storage](/en/enterprise-server@3.22/admin/managing-github-actions-for-your-enterprise/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-google-cloud-storage) You can enable GitHub Actions on GitHub Enterprise Server and use Google Cloud Storage to store data generated by workflow runs. * [Enabling GitHub Actions with MinIO storage](/en/enterprise-server@3.22/admin/managing-github-actions-for-your-enterprise/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage) You can enable GitHub Actions on GitHub Enterprise Server and use MinIO storage to store data generated by workflow runs. * [Managing self-hosted runners for Dependabot updates on your enterprise](/en/enterprise-server@3.22/admin/managing-github-actions-for-your-enterprise/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates) You can create dedicated runners for GitHub.com that Dependabot uses to create pull requests to help secure and maintain the dependencies used in repositories on your enterprise. * [About using actions in your enterprise](/en/enterprise-server@3.22/admin/managing-github-actions-for-your-enterprise/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise) GitHub Enterprise Server includes most GitHub-authored actions, and has options for enabling access to other actions from GitHub.com and GitHub Marketplace. * [Enabling automatic access to GitHub.com actions using GitHub Connect](/en/enterprise-server@3.22/admin/managing-github-actions-for-your-enterprise/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect) To allow GitHub Actions in your enterprise to use actions from GitHub.com, you can connect your enterprise instance to GitHub Enterprise Cloud. * [Manually syncing actions from GitHub.com](/en/enterprise-server@3.22/admin/managing-github-actions-for-your-enterprise/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom) For users that need access to actions from GitHub.com, you can sync specific actions to your enterprise. * [Using the latest version of the official bundled actions](/en/enterprise-server@3.22/admin/managing-github-actions-for-your-enterprise/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions) You can update the actions that are bundled with your enterprise, or use actions directly from GitHub.com. * [Setting up the tool cache on self-hosted runners without internet access](/en/enterprise-server@3.22/admin/managing-github-actions-for-your-enterprise/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access) To use the included `actions/setup` actions on self-hosted runners without internet access, you must first populate the runner's tool cache for your workflows. * [High availability for GitHub Actions](/en/enterprise-server@3.22/admin/managing-github-actions-for-your-enterprise/advanced-configuration-and-troubleshooting/high-availability-for-github-actions) There are some special considerations for administering GitHub Actions in a high availability configuration. * [Backing up and restoring GitHub Enterprise Server with GitHub Actions enabled](/en/enterprise-server@3.22/admin/managing-github-actions-for-your-enterprise/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled) To restore a backup of GitHub.com when GitHub Actions is enabled, you must configure GitHub Actions before restoring the backup with GitHub Enterprise Server Backup Utilities. * [Using a staging environment](/en/enterprise-server@3.22/admin/managing-github-actions-for-your-enterprise/advanced-configuration-and-troubleshooting/using-a-staging-environment) Learn about using GitHub Actions with GitHub Enterprise Server staging instances. * [Troubleshooting GitHub Actions for your enterprise](/en/enterprise-server@3.22/admin/managing-github-actions-for-your-enterprise/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise) Troubleshooting common issues that occur when using GitHub Actions on GitHub Enterprise Server. * [Updating the credentials for GitHub Actions storage](/en/enterprise-server@3.22/admin/managing-github-actions-for-your-enterprise/advanced-configuration-and-troubleshooting/updating-the-credentials-for-github-actions-storage) If your credentials for connecting to GitHub Actions storage change, you must update the credentials in the configuration on GitHub Enterprise Server. * [Migrating GitHub Actions external storage](/en/enterprise-server@3.22/admin/managing-github-actions-for-your-enterprise/advanced-configuration-and-troubleshooting/migrating-github-actions-external-storage) Migrate GitHub Actions external storage within the same provider to consolidate accounts, meet residency requirements, or reorganize storage tenancy while keeping existing workflow logs and artifacts accessible. * [Getting started with GitHub Packages for your enterprise](/en/enterprise-server@3.22/admin/configuring-packages/getting-started-with-github-packages-for-your-enterprise) You can start using GitHub Packages on GitHub.com by enabling the feature, configuring third-party storage, configuring the ecosystems you want to support, and updating your TLS certificate. * [Enabling GitHub Packages with AWS](/en/enterprise-server@3.22/admin/configuring-packages/enabling-github-packages-with-aws) Set up GitHub Packages with AWS as your external storage. * [Enabling GitHub Packages with Azure Blob Storage](/en/enterprise-server@3.22/admin/configuring-packages/enabling-github-packages-with-azure-blob-storage) Set up GitHub Packages with Azure Blob Storage as your external storage. * [Enabling GitHub Packages with MinIO](/en/enterprise-server@3.22/admin/configuring-packages/enabling-github-packages-with-minio) Set up GitHub Packages with MinIO as your external storage. * [Configuring package ecosystem support for your enterprise](/en/enterprise-server@3.22/admin/configuring-packages/configuring-package-ecosystem-support-for-your-enterprise) You can configure GitHub Packages for your enterprise by globally enabling or disabling individual package ecosystems on your enterprise, including Container registry, Docker, and npm. Learn about other configuration requirements to support specific package ecosystems. * [Migrating your enterprise to the Container registry from the Docker registry](/en/enterprise-server@3.22/admin/configuring-packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry) You can migrate Docker images previously stored in the Docker registry on GitHub.com to the Container registry. * [Release notes](/en/enterprise-server@3.22/admin/release-notes) Detailed information for all releases of the currently selected version of GitHub Enterprise Server. * [GitHub Enterprise Server releases](/en/enterprise-server@3.22/admin/all-releases) Review information for each version of GitHub Enterprise Server: closing down dates, links to documentation, and minimum recommended versions of supporting applications.