docs/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md

title, intro, permissions, redirect_from, versions, type, topics, shortTitle

title	intro	permissions	redirect_from	versions	type	topics	shortTitle
Enabling automatic access to GitHub.com actions using GitHub Connect	To allow {% data variables.product.prodname_actions %} in your enterprise to use actions from {% data variables.product.prodname_dotcom_the_website %}, you can connect your enterprise instance to {% data variables.product.prodname_ghe_cloud %}.	Site administrators for {% data variables.product.product_name %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable access to all {% data variables.product.prodname_dotcom_the_website %} actions.	/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect /admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect	ghes ghae * next	how_to	Actions Enterprise GitHub Connect	Use GitHub Connect for actions

{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}

By default, {% data variables.product.prodname_actions %} workflows on {% data variables.product.product_name %} cannot use actions directly from {% data variables.product.prodname_dotcom_the_website %} or {% data variables.product.prodname_marketplace %}.

To make all actions from {% data variables.product.prodname_dotcom_the_website %} available on your enterprise instance, you can use {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %}. For other ways of accessing actions from {% data variables.product.prodname_dotcom_the_website %}, see "About using actions in your enterprise."

Enabling automatic access to all {% data variables.product.prodname_dotcom_the_website %} actions

{% data reusables.actions.enterprise-github-connect-warning %}

Before enabling access to all actions from {% data variables.product.prodname_dotcom_the_website %} on your enterprise instance, you must connect your enterprise to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "Connecting your enterprise to {% data variables.product.prodname_ghe_cloud %}."

{% data reusables.enterprise-accounts.access-enterprise %} {%- ifversion ghes < 3.1 %} {% data reusables.enterprise-accounts.settings-tab %} {%- endif %} {% data reusables.enterprise-accounts.github-connect-tab %} {%- ifversion ghes > 3.0 or ghae %}

1. Under "Users can utilize actions from GitHub.com in workflow runs", use the drop-down menu and select Enabled. {%- else %}
2. Under "Server can use actions from GitHub.com in workflows runs", use the drop-down menu and select Enabled. {%- endif %}
3. {% data reusables.actions.enterprise-limit-actions-use %}

{% ifversion ghes > 3.2 or ghae-issue-4815 %}

Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website %}

When you enable {% data variables.product.prodname_github_connect %}, users see no change in behavior for existing workflows because {% data variables.product.prodname_actions %} searches {% data variables.product.product_location %} for each action before falling back to {% data variables.product.prodname_dotcom_the_website%}. This ensures that any custom versions of actions your enterprise has created are used in preference to their counterparts on {% data variables.product.prodname_dotcom_the_website%}.

Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website %} blocks the potential for a man-in-the-middle attack by a malicious user with access to {% data variables.product.product_location %}. When an action on {% data variables.product.prodname_dotcom_the_website %} is used for the first time, that namespace is retired in {% data variables.product.product_location %}. This blocks any user creating an organization and repository in your enterprise that matches that organization and repository name on {% data variables.product.prodname_dotcom_the_website %}. This ensures that when a workflow runs, the intended action is always run.

After using an action from {% data variables.product.prodname_dotcom_the_website %}, if you want to create an action in {% data variables.product.product_location %} with the same name, first you need to make the namespace for that organization and repository available.

{% data reusables.enterprise_site_admin_settings.access-settings %} 2. In the left sidebar, under Site admin click Retired namespaces. 3. Locate the namespace that you want use in {% data variables.product.product_location %} and click Unretire. 4. Go to the relevant organization and create a new repository.

{% tip %}

Tip: When you unretire a namespace, always create the new repository with that name as soon as possible. If a workflow calls the associated action on {% data variables.product.prodname_dotcom_the_website %} before you create the local repository, the namespace will be retired again. For actions used in workflows that run frequently, you may find that a namespace is retired again before you have time to create the local repository. In this case, you can temporarily disable the relevant workflows until you have created the new repository.

{% endtip %}

{% endif %}