text stringlengths 12 91.7k | metadata dict |
|---|---|
About role management
You can choose to join an organization owned by your enterprise as a member or as an organization owner, change your role within the organization, or leave the organization. Your organization role determines your level of access to organization resources as follows:
Unaffiliated or no official or... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise.md",
"title": "Managing your role in an organization owned by your enterprise"
} |
1. Under "Users can create organizations", use the drop-down menu and click Enabled or Disabled. | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md",
"title": "Preventing users from creating organizations"
} |
You can remove an organization that is owned by your enterprise account, so the organization stands alone.
Limitations
If you use or , removing organizations from your enterprise is not possible.
If you use , you can instead migrate organizations with the . See AUTOTITLE.
What happens when an organization is removed... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise.md",
"title": "Removing organizations from your enterprise"
} |
When using LDAP or built-in authentication, two-factor authentication is supported on . Organization owners can require members to have two-factor authentication enabled.
For more information, see AUTOTITLE.
Requirements for enforcing two-factor authentication
Before you can require organization members and outside co... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md",
"title": "Requiring two-factor authentication for an organization"
} |
About organization restoration
You can use the site admin dashboard to restore an organization that was previously deleted on , as long as the audit log Elasticsearch indices contain the data for the org.delete event.
Immediately after you restore an organization, the organization will not be exactly the same as it was... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md",
"title": "Restoring a deleted organization"
} |
About temporary access to user-owned repositories
If your enterprise uses , and you've allowed users to create repositories owned by their user accounts, you can temporarily access any user-owned repository within your enterprise.
When you temporarily access a repository, you get admin access to the repository for two ... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-repositories-in-your-enterprise/accessing-user-owned-repositories-in-your-enterprise.md",
"title": "Accessing user-owned repositories in your enterprise"
} |
[!NOTE] Repository policy delegated bypass is in and subject to change.
You can view and manage all requests for bypass privileges on the “Bypass Requests" page, located under the Policy settings.
Filter requests by approver (member of the bypass list), requester (contributor making the request), timeframe, and status... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-repositories-in-your-enterprise/bypass-push-rules-requests.md",
"title": "Managing requests to bypass push rules"
} |
About
You can use with a single repository, all of your personal or organization repositories, or with every repository in your enterprise. Before you can enable for specific repositories or organizations, you need to enable for your enterprise.
For more information, see AUTOTITLE, AUTOTITLE, and the project site... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md",
"title": "Configuring Git Large File Storage for your enterprise"
} |
Disabling Git SSH access to a specific repository
1. Under "Git SSH access", select the drop-down menu, and click Disabled.
Disabling Git SSH access to all repositories owned by a user or organization
1. Under "Git SSH access", select the drop-down menu, and click Disabled.
1. Select Enforce on all repositories.
!S... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md",
"title": "Disabling Git SSH access on your enterprise"
} |
Examples
How will I target repositories?
First, you'll target organizations in your enterprise. You can select all organizations, choose from a list, or create a dynamic rule using fnmatch syntax. If you use , you can also choose to target all repositories owned by users in your enterprise.
Then, you'll target reposit... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-repositories-in-your-enterprise/governing-how-people-use-repositories-in-your-enterprise.md",
"title": "Governing how people use repositories in your enterprise"
} |
Locking a repository
1. In the "Single Repository Lock" section, click Lock.
Unlocking a repository
1. In the "Single Repository Lock" section, click Unlock. | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-repositories-in-your-enterprise/locking-a-repository.md",
"title": "Locking a repository"
} |
Custom properties allow you to decorate your repositories with information such as compliance frameworks, data sensitivity, or project details. Custom properties are private and can only be viewed by people with read permissions to the repository. An enterprise can have up to 100 property definitions. An allowed value ... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-repositories-in-your-enterprise/managing-custom-properties-for-repositories-in-your-enterprise.md",
"title": "Managing custom properties for repositories in your enterprise"
} |
About repository restoration
Usually, if someone deletes a repository, it will be available on disk for 90 days and can be restored via the site admin dashboard. For more information, see AUTOTITLE.
Unless a legal hold is in effect on a user or organization, after 90 days the repository is purged and deleted forever.
I... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md",
"title": "Restoring a deleted repository"
} |
Getting information on deliveries
You can find information for the last response of all service hooks deliveries on any repository.
1. Under the service hook having problems, click Latest Delivery.
1. Under Remote Calls, you'll see the headers that were used when POSTing to the remote server along with the response tha... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md",
"title": "Troubleshooting service hooks"
} |
If your enterprise uses , and you've allowed users to create repositories owned by their user accounts, you can view all user-owned repositories within your enterprise.
You can also temporarily access any user-owned repository. For more information, see AUTOTITLE. | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-repositories-in-your-enterprise/viewing-user-owned-repositories-in-your-enterprise.md",
"title": "Viewing user-owned repositories in your enterprise"
} |
About roles in an enterprise
offers a range of predefined and custom roles for access to enterprise settings and resources.
Role Description
---- -----------
Enterprise owner Can manage all enterprise settings, members, and policies.
Billing manager Can manage enterprise billing settings.
App manager Can... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-roles-in-your-enterprise/abilities-of-roles.md",
"title": "Abilities of roles in an enterprise"
} |
Enterprise owners can assign custom and predefined enterprise roles to users and teams. Some roles can be assigned to enterprise teams, whereas other roles are only available for individual users. Find the section below for the role you want to assign.
For more information about using roles effectively, see AUTOTITLE.
... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-roles-in-your-enterprise/assign-roles.md",
"title": "Assigning roles to people in an enterprise"
} |
To tailor access management to your company's needs, you can create custom roles for your enterprise account and organizations.
Custom roles are sets of permissions for settings and resources that you can assign to users and teams. To learn best practices for using roles on , see AUTOTITLE.
Creating enterprise custom ... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-roles-in-your-enterprise/create-custom-roles.md",
"title": "Creating custom roles in an enterprise"
} |
Roles control people's access to settings and resources in your enterprise and organizations. For an introduction to roles, see AUTOTITLE.
By using roles effectively, you can:
Delegate administrative duties and manage access securely at every level of your enterprise.
Harden security by reducing the number of people ... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-roles-in-your-enterprise/identify-role-requirements.md",
"title": "Identifying the roles required by your enterprise"
} |
About reserved usernames
reserves certain usernames for internal use. You cannot assign reserved usernames to users or organizations on your instance. For example, the following words are reserved:
admin
enterprise
login
staff
support
Viewing reserved username
You can view a full list of reserved usernames for .... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/about-reserved-usernames-for-github-enterprise-server.md",
"title": "About reserved usernames for GitHub Enterprise Server"
} |
Once initiated, the audit disables all existing SSH keys and forces users to approve or reject them before they're able to clone, pull, or push to any repositories. An audit is useful in situations where an employee or contractor leaves the company and you need to ensure that all keys are verified.
Initiating an audit... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/auditing-ssh-keys.md",
"title": "Auditing SSH keys"
} |
Accessing the audit log
The audit log dashboard gives you a visual display of audit data across your enterprise.
Within the map, you can pan and zoom to see events around the world. Hover over a country to see a quick count of events from that country.
Searching for events across your enterprise
The audit log lists th... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md",
"title": "Auditing users across your enterprise"
} |
Enabling two-factor authentication
Two-factor authentication (2FA) is a way of logging in to websites and services that requires a second factor beyond a password for authentication. In 's case, this second factor is a one time authentication code generated by an application on a user's smartphone. We strongly recommen... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/best-practices-for-user-security.md",
"title": "Best practices for user security"
} |
To simplify administration at scale, you can create enterprise teams.
Adding a user to a team grants them the privileges associated with the team. Removing a user from a team removes those privileges, but does not remove the user from the enterprise account.
<!-- If the team size limit changes, also update the referen... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/create-enterprise-teams.md",
"title": "Creating enterprise teams"
} |
What happens when I delete a user account?
Deleting a user account removes all repositories, forks of private repositories, wikis, issues, pull requests, pages, and packages and container images owned by the user account. By deleting a user account, you may break software projects and workflows that depend on these thi... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/deleting-users-from-your-instance.md",
"title": "Deleting users from your instance"
} |
About guest collaborators
Enabling guest collaborators in your IdP
If you use Microsoft Entra ID (previously known as Azure AD) or Okta for authentication, you may need update the application in your IdP.
Enabling guest collaborators with Entra ID
Enabling guest collaborators with Okta
Enabling guest collaborators... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/enabling-guest-collaborators.md",
"title": "Enabling guest collaborators"
} |
About export of membership information
You can export aggregated information about your enterprise's members as a membership information report. For example, you may want to perform an audit of your enterprise's current members. You can generate a file containing the report from 's web UI.
The membership information re... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/exporting-membership-information-for-your-enterprise.md",
"title": "Exporting membership information for your enterprise"
} |
About user impersonation
If you need to temporarily take over a user account, for example when troubleshooting a user problem, or when the user is unavailable and urgent action is required, you can start an impersonation session to act on their behalf.
For each impersonation session, you need to provide a reason for th... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/impersonating-a-user.md",
"title": "Impersonating a user"
} |
You can invite people directly to your enterprise as unaffiliated users. You can then add these users to organizations or enterprise teams and assign licenses to them. For more information about unaffiliated users, see AUTOTITLE.
Inviting users
[!NOTE] These steps apply to enterprises that use personal accounts. If y... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/invite-users-directly.md",
"title": "Inviting users to your enterprise directly"
} |
About administrator management
If you do not use , youYou can add or remove enterprise owners and billing managers in your enterprise. For more information about the privileges that come with each enterprise role, see AUTOTITLE.
If you want to manage enterprise owners and billing managers for an enterprise account on ,... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md",
"title": "Inviting people to manage your enterprise"
} |
About dormant users
[!NOTE] You cannot mark a dormant user as active. To become active, a user must perform one of the activities listed above.
When assessing user dormancy, we only consider organizations, repositories, or sign-on events that are associated with the enterprise. For example, a user who has recently com... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/managing-dormant-users.md",
"title": "Managing dormant users"
} |
You can manage invitations to your enterprise or organizations within your enterprise.
For more information about viewing people in your enterprise or managing enterprise owners and billing managers, see AUTOTITLE and AUTOTITLE.
For more information about adding or removing members from your organization, see AUTOTITLE... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/managing-invitations-to-organizations-within-your-enterprise.md",
"title": "Managing invitations to organizations within your enterprise"
} |
About support entitlements
People with support entitlements for your enterprise account can use the support portal to open, view, and comment on support tickets associated with the enterprise account.
Enterprise owners and billing managers automatically have a support entitlement. Enterprise owners can add support enti... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md",
"title": "Managing support entitlements for your enterprise"
} |
Usually, if someone deletes a repository, it will be available on disk for 90 days and can be restored via the site admin dashboard. After 90 days the repository is purged and deleted forever. If you place a legal hold on a user or organization, repositories they own are available for restore indefinitely.
1. Under "Le... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/placing-a-legal-hold-on-a-user-or-organization.md",
"title": "Placing a legal hold on a user or organization"
} |
[!NOTE] For information about promoting a user to an organization owner, see the ghe-org-admin-promote section of AUTOTITLE.
Considerations with external authentication
If you use certain external authentication features, you may not be able to manage promotion and demotion from the enterprise settings or command line... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md",
"title": "Promoting or demoting a site administrator"
} |
Whenever a commit is pushed to , it is linked to a user account if they are both associated with the same email address. However, existing commits are not retroactively linked when a user registers a new email address or creates a new account.
1. To the right of "Rebuild commit contributions data", click Rebuild.
You s... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/rebuilding-contributions-data.md",
"title": "Rebuilding contributions data"
} |
The recommended offboarding approach for your enterprise depends on whether you use personal accounts or . To learn more about the effects of offboarding users, see AUTOTITLE.
Removing a member from an enterprise with personal accounts
When you remove a member from your enterprise, the member is removed from all organ... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/removing-a-member-from-your-enterprise.md",
"title": "Removing a member from your enterprise"
} |
About suspended users
If employees leave the company, you can suspend their accounts to open up user licenses in your license while preserving the issues, comments, repositories, gists, and other data they created. Suspended users cannot sign into your instance, nor can they push or pull code.
When you suspend a user... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md",
"title": "Suspending and unsuspending users"
} |
About SAML access to your enterprise account
When you enable SAML single sign-on for your enterprise account, each enterprise member can link their external identity on your identity provider (IdP) to their existing account on .
If your enterprise uses , your members will use accounts provisioned through your IdP. wi... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md",
"title": "Viewing and managing a user's SAML access to your enterprise"
} |
About the list of people in your enterprise
To audit access to your enterprise's resources and manage license usage, you can see a list of all the people who have access to your enterprise.
You can see all current enterprise members and enterprise administrators, as well as pending invitations to become members and adm... | {
"source": "github-docs/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md",
"title": "Viewing people in your enterprise"
} |
About backups of when using
You can use to back up and restore the data and configuration for to a new instance. For more information, see AUTOTITLE.
However, not all the data for is included in these backups.
Restoring a backup of when is enabled
To restore a backup of with , you must manually configure netw... | {
"source": "github-docs/admin/managing-github-actions-for-your-enterprise/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md",
"title": "Backing up and restoring GitHub Enterprise Server with GitHub Actions enabled"
} |
Replication or redundancy of your data
We strongly recommend that you configure your external storage to use data redundancy or replication. For more information, refer to your storage provider's documentation:
Azure Storage redundancy documentation
Amazon S3 replication documentation
High availability replicas
P... | {
"source": "github-docs/admin/managing-github-actions-for-your-enterprise/advanced-configuration-and-troubleshooting/high-availability-for-github-actions.md",
"title": "High availability for GitHub Actions"
} |
About migrating external storage
You can migrate external storage to a new bucket, account, or region on the same provider when consolidating cloud accounts, meeting residency requirements, or reorganizing storage tenancy.
The migration works because identifies stored objects by their key (path) within a bucket or c... | {
"source": "github-docs/admin/managing-github-actions-for-your-enterprise/advanced-configuration-and-troubleshooting/migrating-github-actions-external-storage.md",
"title": "Migrating GitHub Actions external storage"
} |
Checking the health of
You can check the health of on with the ghe-actions-check command-line utility. For more information, see AUTOTITLE and AUTOTITLE.
Configuring self-hosted runners when using a self-signed certificate for
For more information, see AUTOTITLE.
Installing the certificate on the runner machine
... | {
"source": "github-docs/admin/managing-github-actions-for-your-enterprise/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md",
"title": "Troubleshooting GitHub Actions for your enterprise"
} |
Updating the credential secret for your storage provider
To update the credential secret for your storage provider on , you have two options.
[!WARNING]
This process is only for updating the secret key used to authenticate to your existing external storage provider. It assumes that your networking configuration, sto... | {
"source": "github-docs/admin/managing-github-actions-for-your-enterprise/advanced-configuration-and-troubleshooting/updating-the-credentials-for-github-actions-storage.md",
"title": "Updating the credentials for GitHub Actions storage"
} |
About staging environments for
It can be useful to have a staging or testing environment for , so that you can test updates or new features before implementing them in your production environment. For more information, see AUTOTITLE.
[!TIP]
If you are migrating external storage to a new bucket, account, or region o... | {
"source": "github-docs/admin/managing-github-actions-for-your-enterprise/advanced-configuration-and-troubleshooting/using-a-staging-environment.md",
"title": "Using a staging environment"
} |
[!TIP]
If is already configured and you need to move its data to a new bucket, account, or region on Amazon S3, see AUTOTITLE.
Prerequisites
[!NOTE]
The only -supported S3 storage providers are Amazon S3 and MinIO Gateway for NAS.
Before enabling , make sure you have completed the following steps:
Create your Ama... | {
"source": "github-docs/admin/managing-github-actions-for-your-enterprise/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md",
"title": "Enabling GitHub Actions with Amazon S3 storage"
} |
[!TIP]
If is already configured and you need to move its data to a new storage account or region on Azure Blob Storage, see AUTOTITLE.
Prerequisites
Before enabling , make sure you have completed the following steps:
Create your Azure storage account for storing workflow data. stores its data as block blobs, and t... | {
"source": "github-docs/admin/managing-github-actions-for-your-enterprise/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage.md",
"title": "Enabling GitHub Actions with Azure Blob storage"
} |
[!NOTE]
support for Google Cloud Storage is currently in and subject to change.
[!TIP]
If is already configured and you need to move its data to a new bucket, project, or region on Google Cloud Storage, see AUTOTITLE.
Prerequisites
Before enabling , make sure you have completed the following steps:
Create your ... | {
"source": "github-docs/admin/managing-github-actions-for-your-enterprise/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-google-cloud-storage.md",
"title": "Enabling GitHub Actions with Google Cloud Storage"
} |
[!TIP]
If is already configured and you need to move its data to a new MinIO bucket or deployment, see AUTOTITLE.
Prerequisites
Before enabling , make sure you have completed the following steps:
Create your MinIO bucket for storing data generated by workflow runs. For more information about installing and configur... | {
"source": "github-docs/admin/managing-github-actions-for-your-enterprise/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md",
"title": "Enabling GitHub Actions with MinIO storage"
} |
About self-hosted runners for
You can help users of to create and maintain secure code by setting up security and version updates. With , developers can configure repositories so that their dependencies are updated and kept secure automatically. For more information, see AUTOTITLE.
To use on , you must configure se... | {
"source": "github-docs/admin/managing-github-actions-for-your-enterprise/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md",
"title": "Managing self-hosted runners for Dependabot updates on your enterprise"
} |
About for enterprises
Task More information
---- ----------------
Automatically test and build your application AUTOTITLE
Deploy your application AUTOTITLE
Automatically and securely package code into artifacts and containers AUTOTITLE
helps your team work faster at scale. When large repositories start... | {
"source": "github-docs/admin/managing-github-actions-for-your-enterprise/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md",
"title": "About GitHub Actions for enterprises"
} |
About on
is enabled for your enterprise by default. To get started using within your enterprise, you can manage the policies that control how enterprise members use and optionally add self-hosted runners to run workflows.
Managing policies for
You can use policies to control how enterprise members use . For exam... | {
"source": "github-docs/admin/managing-github-actions-for-your-enterprise/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud.md",
"title": "Getting started with GitHub Actions for GitHub Enterprise Cloud"
} |
About on
This article explains how site administrators can configure to use .
You'll need to determine whether your instance has adequate CPU and memory resources to handle the load from without causing performance loss, and possibly increase those resources. You'll also need to decide which storage provider you'l... | {
"source": "github-docs/admin/managing-github-actions-for-your-enterprise/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md",
"title": "Getting started with GitHub Actions for GitHub Enterprise Server"
} |
About self-hosted runners for
For more information, see AUTOTITLE.
With , developers can write and combine individual tasks called actions to create custom workflows. To enable for , you must host at least one machine to execute jobs. You can host your own runner machine to execute jobs, and thisThis machine is cal... | {
"source": "github-docs/admin/managing-github-actions-for-your-enterprise/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md",
"title": "Getting started with self-hosted runners for your enterprise"
} |
About for enterprises
With , your enterprise can automate, customize, and execute your software development workflows like testing and deployments. For more information, see AUTOTITLE.
Before you introduce to a large enterprise, you first need to plan your adoption and make decisions about how your enterprise will u... | {
"source": "github-docs/admin/managing-github-actions-for-your-enterprise/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md",
"title": "Introducing GitHub Actions to your enterprise"
} |
About enterprise migrations to
To migrate your enterprise to from an existing system, you can plan the migration, complete the migration, and retire existing systems.
This guide addresses specific considerations for migrations. For additional information about introducing to your enterprise, see AUTOTITLE.
Planning... | {
"source": "github-docs/admin/managing-github-actions-for-your-enterprise/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md",
"title": "Migrating your enterprise to GitHub Actions"
} |
About actions on
workflows can use actions, which are individual tasks that you can combine to create jobs and customize your workflow. You can create your own actions, or use and customize actions shared by the community.
You can restrict your developers to using actions that are stored on , which includes most of... | {
"source": "github-docs/admin/managing-github-actions-for-your-enterprise/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md",
"title": "About using actions in your enterprise"
} |
About automatic access to actions
By default, workflows on cannot use actions directly from or . To make public actions from available on your enterprise instance, you can use to integrate with .
Alternatively, if you want stricter control over which actions are allowed in your enterprise, you can manually downl... | {
"source": "github-docs/admin/managing-github-actions-for-your-enterprise/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md",
"title": "Enabling automatic access to GitHub.com actions using GitHub Connect"
} |
We recommend enabling automatic access to public actions by using to integrate with . See AUTOTITLE.
If you want stricter control over which actions are allowed in your enterprise, you can follow this guide to use our open source actions-sync tool to sync individual action repositories from to your enterprise.
When ... | {
"source": "github-docs/admin/managing-github-actions-for-your-enterprise/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md",
"title": "Manually syncing actions from GitHub.com"
} |
About the included setup actions and the runner tool cache
Most official -authored actions are automatically bundled with . However, self-hosted runners without internet access require some configuration before they can use the included actions/setup-LANGUAGE actions, such as setup-node.
The actions/setup-LANGUAGE acti... | {
"source": "github-docs/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.md",
"title": "Setting up the tool cache on self-hosted runners without internet access"
} |
Your enterprise instance includes a number of built-in actions that you can use in your workflows. For more information about the bundled actions, see AUTOTITLE.
These bundled actions are a point-in-time snapshot of the official actions found at https://github.com/actions, so there may be newer versions of these action... | {
"source": "github-docs/admin/managing-github-actions-for-your-enterprise/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md",
"title": "Using the latest version of the official bundled actions"
} |
About managers
Enterprise owners can designate other users in their enterprise as managers for apps.
An app manager:
Can manage the settings for a registration that is owned by the enterprise. For the specific app settings that managers can control, see AUTOTITLE.
Cannot install and uninstall on an enterprise or... | {
"source": "github-docs/admin/managing-github-apps-for-your-enterprise/adding-and-removing-github-app-managers-in-your-enterprise.md",
"title": "Adding and removing GitHub App managers in your enterprise"
} |
Introduction
To automate a process securely, you can create a owned by an enterprise account, then install the app in the enterprise or organization where the automation will take place.
provide tokens that you can use to authenticate API calls to in scripts and workflows. These tokens are suitable for enterprises w... | {
"source": "github-docs/admin/managing-github-apps-for-your-enterprise/automate-installations.md",
"title": "Automating app installations in your enterprise's organizations"
} |
You can create a under your enterprise account. The app can only be installed on your enterprise or organizations within your enterprise, and can only be authorized by members of your enterprise. The app can't be installed on user accounts.
Step 1: Registering a
To create a , you must first register the app. See AUT... | {
"source": "github-docs/admin/managing-github-apps-for-your-enterprise/creating-github-apps-for-your-enterprise.md",
"title": "Creating GitHub Apps for your enterprise"
} |
About support for Conditional Access Policies
supports CAP for any where OIDC SSO is enabled. Enterprise owners can choose to use this IP allow list configuration instead of 's IP allow list, and can do so once OIDC SSO is configured. For more information about IP allow lists, see AUTOTITLE and AUTOTITLE.
enforces ... | {
"source": "github-docs/admin/managing-iam/configuring-authentication-for-enterprise-managed-users/about-support-for-your-idps-conditional-access-policy.md",
"title": "About support for your IdP's Conditional Access Policy"
} |
About OIDC for Enterprise Managed Users
With , your enterprise uses your identity provider (IdP) to authenticate all members. You can use OpenID Connect (OIDC) to manage authentication for your . Enabling OIDC SSO is a one-click setup process with certificates managed by and your IdP.
See AUTOTITLE.
You can adjust th... | {
"source": "github-docs/admin/managing-iam/configuring-authentication-for-enterprise-managed-users/configuring-oidc-for-enterprise-managed-users.md",
"title": "Configuring OIDC for Enterprise Managed Users"
} |
Before following the steps in this article, make sure that your enterprise uses managed users and that you are signed in as the setup user whose username is your enterprise's shortcode suffixed with admin. You can verify you are signed in with the correct user by checking whether your enterprise view has the "Viewing a... | {
"source": "github-docs/admin/managing-iam/configuring-authentication-for-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users.md",
"title": "Configuring SAML single sign-on for Enterprise Managed Users"
} |
[!WARNING]
Enabling SAML affects all members of your enterprise.
doesn't provide a backup sign in URL where members of your enterprise can sign in using their regular username and password.
If you are unable to sign in, contact via the for assistance.
Supported features
The application on Okta supports SP-initiate... | {
"source": "github-docs/admin/managing-iam/configuring-authentication-for-enterprise-managed-users/configuring-saml-single-sign-on-with-okta-for-enterprise-managed-users.md",
"title": "Configuring SAML single sign-on with Okta for Enterprise Managed Users"
} |
About disabled authentication for
After you disable SAML or OIDC authentication for your enterprise, the following effects apply:
All external identities for the enterprise, and associated email addresses for , will be removed. For more information, see AUTOTITLE.
All will be suspended. The suspended accounts will ... | {
"source": "github-docs/admin/managing-iam/configuring-authentication-for-enterprise-managed-users/disabling-authentication-and-provisioning-for-enterprise-managed-users.md",
"title": "Disabling authentication for Enterprise Managed Users"
} |
You can adjust the lifetime of a session, and how often a managed user account needs to reauthenticate with your IdP, by changing the lifetime policy property of the ID tokens issued for from your IdP. The default lifetime is one hour.
You will need the object ID associated with your OIDC app to complete these steps.... | {
"source": "github-docs/admin/managing-iam/configuring-authentication-for-enterprise-managed-users/finding-the-object-id-for-your-entra-oidc-application.md",
"title": "Finding the object ID for your Entra OIDC application"
} |
About SAML configuration
To use SAML single sign-on (SSO) for authentication to , you must configure both your external SAML identity provider (IdP) and your enterprise or organization on . In a SAML configuration, functions as a SAML service provider (SP). For more information about authentication for your enterprise... | {
"source": "github-docs/admin/managing-iam/iam-configuration-reference/saml-configuration-reference.md",
"title": "SAML configuration reference"
} |
[!NOTE]
This article only applies to . If you use without , usernames are created by users, not .
About usernames with external authentication
You can configure external authentication for using CAS, LDAP, or SAML. For more information, see AUTOTITLE.
When you use external authentication, automatically creates a u... | {
"source": "github-docs/admin/managing-iam/iam-configuration-reference/username-considerations-for-external-authentication.md",
"title": "Username considerations for external authentication"
} |
About recovery codes
You can use a recovery code to access your enterprise account when an authentication configuration error or an issue with your identity provider (IdP) prevents you from using SSO.
In order to access your enterprise account this way, you must have previously downloaded and stored the recovery codes ... | {
"source": "github-docs/admin/managing-iam/managing-recovery-codes-for-your-enterprise/accessing-your-enterprise-account-if-your-identity-provider-is-unavailable.md",
"title": "Accessing your enterprise account if your identity provider is unavailable"
} |
In the event that your IdP is unavailable, you can use a recovery code to sign in and access your enterprise on . For more information, see AUTOTITLE.
If you did not save your recovery codes when you configured SSO, you can still access the codes from your enterprise's settings.
Downloading codes for an enterprise wit... | {
"source": "github-docs/admin/managing-iam/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes.md",
"title": "Downloading your enterprise account's single sign-on recovery codes"
} |
About authentication and user provisioning with Entra ID
Entra ID is a service from Microsoft that allows you to centrally manage user accounts and access to web applications. For more information, see What is Microsoft Entra ID? in the Microsoft Docs.
For more information, see AUTOTITLE.
Prerequisites
The general pre... | {
"source": "github-docs/admin/managing-iam/provisioning-user-accounts-with-scim/configuring-authentication-and-provisioning-with-entra-id.md",
"title": "Configuring authentication and provisioning with Entra ID"
} |
For more information, see AUTOTITLE.AUTOTITLE.
Overview
This guide will help you to set up both SAML authentication and SCIM provisioning for on PingFederate.
Before you start, please note the following:
The use of PingFederate as an IdP for is in . Please contact your account team to provide feedback.
This guide ... | {
"source": "github-docs/admin/managing-iam/provisioning-user-accounts-with-scim/configuring-authentication-and-provisioning-with-pingfederate.md",
"title": "Configuring authentication and provisioning with PingFederate"
} |
If you use a partner IdP, you can simplify the configuration of SCIM provisioning by using the partner IdP's application. If you don't use a partner IdP for provisioning, you can implement SCIM using calls to 's REST API for SCIM. For more information, see AUTOTITLE.AUTOTITLE.
Who needs to follow these instructions?
E... | {
"source": "github-docs/admin/managing-iam/provisioning-user-accounts-with-scim/configuring-scim-provisioning-for-users.md",
"title": "Configuring SCIM provisioning {% ifversion ghec %}for Enterprise Managed Users{% else %}to manage users{% endif %}"
} |
About provisioning with Okta
If you use Okta as an IdP, you can use Okta's application to provision user accounts, manage enterprise membership, and manage team memberships for organizations in your enterprise. Okta is a partner IdP, so you can simplify your authentication and provisioning configuration by using the Ok... | {
"source": "github-docs/admin/managing-iam/provisioning-user-accounts-with-scim/configuring-scim-provisioning-with-okta.md",
"title": "Configuring {% ifversion ghec %}SCIM{% else %}authentication and{% endif %} provisioning with Okta"
} |
If you use have enabled SCIM for , you will use SCIM to:
Deprovision users and groups to remove their access.
Reprovision users that were previously deprovisioned.
Before you deprovision a user, it's important to understand the effects of deprovisioning, which depend on the type of deprovisioning API call that recei... | {
"source": "github-docs/admin/managing-iam/provisioning-user-accounts-with-scim/deprovisioning-and-reinstating-users.md",
"title": "Deprovisioning and reinstating users with SCIM"
} |
How do I disable SCIM?
To disable SCIM provisioning while keeping SAML on:
4. Deselect Enable SCIM configuration.
When this happens, users will still be able to use SAML single sign-on through your identity provider, but SCIM provisioning will no longer work. Instead, SAML JIT provisioning will be used again. For more ... | {
"source": "github-docs/admin/managing-iam/provisioning-user-accounts-with-scim/disabling-scim-provisioning-for-users.md",
"title": "Disabling SCIM provisioning for users"
} |
About team management with SCIM
The following sections explain how uses SCIM provisioning and reconciliation jobs to keep team and organization membership in sync with your IdP.
When receives a Group SCIM API call from your IdP, it generates an externalgroup.scimapisuccess or externalgroup.scimapifailure event in the... | {
"source": "github-docs/admin/managing-iam/provisioning-user-accounts-with-scim/managing-team-memberships-with-identity-provider-groups.md",
"title": "Managing team memberships with identity provider groups"
} |
About migrating from LDAP to SAML and SCIM
If your instance currently uses LDAP authentication, you can migrate to SAML single sign-on (SSO) with SCIM provisioning for enhanced user lifecycle management capabilities. This migration allows you to automatically provision, update, and deprovision user accounts from your ... | {
"source": "github-docs/admin/managing-iam/provisioning-user-accounts-with-scim/migrating-from-ldap-to-saml-with-scim.md",
"title": "Migrating from LDAP to SAML with SCIM"
} |
[!NOTE]
About IAM for
If your enterprise on is created for , you must configure an external identity management system to provision and maintain user accounts. Your identity management system must offer the following functionality:
Single sign-on authentication implementing one of the following two single sign-on ... | {
"source": "github-docs/admin/managing-iam/provisioning-user-accounts-with-scim/provisioning-users-and-groups-with-scim-using-the-rest-api.md",
"title": "Provisioning users and groups with SCIM using the REST API"
} |
About management of team membership with IdP groups
You can review a list of teams that you've synchronized to IdP groups from your enterprise's settings. For more information, see AUTOTITLE.
also runs a reconciliation job once per day, which synchronizes team membership with IdP group membership that is stored on , ... | {
"source": "github-docs/admin/managing-iam/provisioning-user-accounts-with-scim/troubleshooting-team-membership-with-identity-provider-groups.md",
"title": "Troubleshooting team membership with identity provider groups"
} |
About user provisioning for
If you use SAML single sign-on (SSO) for , you can configure SCIM to automatically create or suspend user accounts and grant access to your instance when you assign or unassign the application on your IdP. For more information about SCIM, see System for Cross-domain Identity Management: Pro... | {
"source": "github-docs/admin/managing-iam/provisioning-user-accounts-with-scim/user-provisioning-with-scim-on-ghes.md",
"title": "About user provisioning with SCIM on GitHub Enterprise Server"
} |
About migration of an from OIDC to SAML
To migrate from OIDC to SAML, you will first disable OIDC, which will suspend all , remove all SCIM-provisioned external groups, and delete linked identities.
Then, you will configure SAML and SCIM. At this time, users, groups, and identities will be re-provisioned.
If you're ne... | {
"source": "github-docs/admin/managing-iam/reconfiguring-iam-for-enterprise-managed-users/migrating-from-oidc-to-saml.md",
"title": "Migrating from OIDC to SAML"
} |
About migration of an from SAML to OIDC
If your uses SAML SSO to authenticate with Entra ID, you can migrate to OIDC.
When you migrate from SAML to OIDC, and groups that were previously provisioned for SAML but are not provisioned by the application will have "(SAML)" appended to their display names.
If you're new... | {
"source": "github-docs/admin/managing-iam/reconfiguring-iam-for-enterprise-managed-users/migrating-from-saml-to-oidc.md",
"title": "Migrating from SAML to OIDC"
} |
About migrations between IdPs and tenants
While using , you may need to migrate your enterprise to a new tenant on your IdP, or to a different identity management system. For example, you might be ready to migrate from a test environment to your production environment, or your company may decide to use a new identity s... | {
"source": "github-docs/admin/managing-iam/reconfiguring-iam-for-enterprise-managed-users/migrating-your-enterprise-to-a-new-identity-provider-or-tenant.md",
"title": "Migrating your enterprise to a new identity provider or tenant"
} |
When your enterprise is affected by a major security incident, you can temporarily block single sign-on for all users except enterprise owners. This allows you to lock down access to your enterprise in order to investigate the incident within a more isolated surface area.
The outcome of this action depends on your ente... | {
"source": "github-docs/admin/managing-iam/respond-to-incidents/lock-down-sso.md",
"title": "Locking down single sign-on in your enterprise"
} |
When your enterprise is affected by a security incident, you can respond by preventing programmatic access to your enterprise or its organizations.
Available actions:
Revoke SSO authorizations to remove access to SSO-protected organization resources for user credentials in your enterprise.
Delete keys and tokens to r... | {
"source": "github-docs/admin/managing-iam/respond-to-incidents/revoke-authorizations-or-tokens.md",
"title": "Revoking SSO authorizations or deleting credentials in your enterprise"
} |
With , you can control the user accounts of your enterprise members through your identity provider (IdP). See AUTOTITLE.
can contribute only to private and internal repositories within their enterprise and their own private repositories. On , they have read-only access to the wider community. These visibility and acc... | {
"source": "github-docs/admin/managing-iam/understanding-iam-for-enterprises/abilities-and-restrictions-of-managed-user-accounts.md",
"title": "Abilities and restrictions of managed user accounts"
} |
About SAML SSO for your enterprise
If your enterprise members manage their own user accounts on , you can configure SAML authentication as an additional access restriction for your enterprise or organization.
For more information, see AUTOTITLE and AUTOTITLE.
Alternatively, you can provision and manage the accounts o... | {
"source": "github-docs/admin/managing-iam/understanding-iam-for-enterprises/about-saml-for-enterprise-iam.md",
"title": "About SAML for enterprise IAM"
} |
Shibboleth
If your IdP supports encrypted assertions, you can configure encrypted assertions on for increased security during the authentication process.
Further reading
AUTOTITLE
SAML Wiki on the OASIS website
System for Cross-domain Identity Management: Protocol (RFC 7644) on the IETF website | {
"source": "github-docs/admin/managing-iam/understanding-iam-for-enterprises/about-saml-for-enterprise-iam.md",
"title": "About SAML for enterprise IAM"
} |
About built-in authentication for users outside your provider
By default, when you enable external authentication for , built-in authentication is disabled for your instance. For more information, see AUTOTITLE.
If you're unable to add specific accounts to your external authentication provider, such as accounts for con... | {
"source": "github-docs/admin/managing-iam/understanding-iam-for-enterprises/allowing-built-in-authentication-for-users-outside-your-provider.md",
"title": "Allowing built-in authentication for users outside your provider"
} |
User accounts on are preserved when you change the authentication method and users will continue to log into the same account as long as their username doesn't change.
If the new method of authentication changes usernames, new accounts will be created. As an administrator, you can rename users through the site admin s... | {
"source": "github-docs/admin/managing-iam/understanding-iam-for-enterprises/changing-authentication-methods.md",
"title": "Changing authentication methods"
} |
Before your developers can use with , you must follow a series of configuration steps.
Create a new enterprise account
To use , you need a separate type of enterprise account with enabled.
You can create an enterprise account by signing up for a trial of . See AUTOTITLE.
Understand where your enterprise is hosted
... | {
"source": "github-docs/admin/managing-iam/understanding-iam-for-enterprises/getting-started-with-enterprise-managed-users.md",
"title": "Getting started with {% data variables.product.prodname_emus %}"
} |
Viewing external identity information for a user
If a user is unable to successfully authenticate using SAML, it may be helpful to view information about the single sign-on identity that's linked to the user's account on . For more information, see AUTOTITLE.
Username conflicts
If your enterprise uses , normalizes th... | {
"source": "github-docs/admin/managing-iam/understanding-iam-for-enterprises/troubleshooting-identity-and-access-management-for-your-enterprise.md",
"title": "Troubleshooting identity and access management for your enterprise"
} |
About built-in authentication
By default, uses built-in authentication. Each person creates a user account on from an invitation or by signing up, and then authenticates with the credentials for the account to access your instance. Your instance stores the authentication information for the account.
By default, user... | {
"source": "github-docs/admin/managing-iam/using-built-in-authentication/configuring-built-in-authentication.md",
"title": "Configuring built-in authentication"
} |
Passkeys are enabled by default.
1. In the "Passkeys" section, deselect Enable passkeys.
Further reading
AUTOTITLE | {
"source": "github-docs/admin/managing-iam/using-built-in-authentication/disabling-passkeys-for-your-instance.md",
"title": "Disabling passkeys for your instance"
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.