GitHub Actions Certification

GitHub Actions in the Enterprise Cloud

Define how to control access to actions within the enterprise

In this guide, you’ll learn how to configure GitHub Actions policies at the enterprise and repository levels. Implementing these controls ensures consistent permission settings, secure workflows, and centralized management across multiple organizations.

1. Enterprise-Level Policies

At the enterprise scope, you can enforce Actions policies for all organizations or only selected ones.

  1. Navigate to Policies → Actions in your enterprise account.
  2. Review the available settings for enabling or disabling GitHub Actions.
  3. Optionally allow organizations to manage self-hosted runners at the repository level.

The image shows a GitHub Enterprise interface with a focus on the "Policies" section under "Actions," where options for enabling GitHub Actions for organizations are displayed.

Here you can:

  • Enable or disable Actions for every organization.
  • Grant or revoke permission to self-manage self-hosted runners.

The image shows a GitHub Enterprise settings page for "Actions," where policies for enabling actions and managing runners are configured. The interface includes options for allowing actions and reusable workflows across organizations.

Note

Enterprise-level policies take precedence over organization and repository settings. Once set, lower levels become read-only and inherit these policies.

1.1 Allowing a Specific Action Across Your Enterprise

To whitelist a single action:

  1. Under Policies → Actions, choose Allow specific actions.
  2. Enter the action reference, for example:
rtcamp/action-slack-notify@v2
  1. Click Save to enforce this setting for all organizations.

The image shows a GitHub Actions settings page for an enterprise account, where policies for enabling actions and workflows are being configured. Various options for allowing actions and reusable workflows are displayed, with a specific action listed for allowance.

To confirm the policy is active:

  1. Go to any organization in your enterprise.
  2. Select Settings → Actions → General.
  3. Observe that organization-level controls are disabled and display your enterprise policy.

2. Repository-Level Policies

If you need more granular control, define Actions permissions per repository—whether under an organization or a personal account.

2.1 Viewing and Selecting Repositories

Start by listing repositories in your organization:

The image shows a GitHub organization page named "kodekloud-training-organization" with a list of repositories. There are seven repositories displayed, including "solar-system" and "enterprise-actions-demo."

2.2 Configuring Actions Permissions

Open the target repository’s Settings → Actions → General to choose:

  • Disable Actions
  • Allow all Actions
  • Allow local Actions only
  • Allow specific Actions and reusable workflows

The image shows a GitHub settings page for a repository, focusing on actions permissions and artifact log retention settings. The "Disable actions" option is selected, and the artifact retention is set to 90 days.

Warning

Disabling Actions at the repository level will prevent any workflows from running, including those critical for CI/CD.

Personal Repository Example

For personal repositories like ga-cloud-deploy-demo, the steps are identical:

  1. Navigate to the repository.
  2. Click Settings → Actions → General.
  3. Set your desired permission level.

The image shows a GitHub repository page titled "ga-cloud-deploy-demo" with a list of files and folders, including workflows, images, and Kubernetes configurations. The repository has 53 commits and is public.

The image shows the "Actions permissions" settings page of a GitHub repository, where various options for allowing or disabling actions and workflows are displayed.

3. Summary of Policy Levels

ScopeApplies ToTypical Use Case
Repository levelIndividual reposCustom workflows, personal projects
Organization level*Multiple repos in one organizationTeam-wide policy enforcement
Enterprise levelAll or selected organizationsGlobal compliance, centralized CI/CD governance

*Organization-level policies are configured under Organization → Settings → Actions.

Watch Video

Watch video content

Previous
Configure organizational use policies for GitHub Actions