> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/keeperpam/privileged-access-manager/getting-started/pam-configuration/github-actions-environment-setup.md).

# GitHub Actions Environment Setup

Setting up your GitHub environment to work with KeeperPAM

## GitHub Environment Overview <a href="#iam-admin-user" id="iam-admin-user"></a>

{% hint style="info" %}
Vault user interface update coming in version 18.8
{% endhint %}

GitHub secrets can be managed by a Keeper Gateway using a specified token configured in the PAM Configuration record. This guide provides step-by-step instructions for configuring the PAM Configuration for your GitHub tenant.

**NOTE**: Currently GitHub PAM can only be used for Universal Secrets Sync.

### Prerequisites

1. Prior to proceeding with this guide, make sure to [install and configure your Keeper Gateway](/keeperpam/privileged-access-manager/getting-started/gateways/one-time-access-token.md).
2. Create a fine-grained personal access token that has the appropriate secrets access. For example:
   * Read and Write access to organization secrets
   * Read access to repository metadata
   * Read and Write access to repository agent secrets

For API Key creation, see [GitHub's documention here](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens).

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2F7LLv5kBVMgMsqJpqwoU6%2FScreenshot%202026-10-01%20at%2010.32.47%E2%80%AFAM.png?alt=media&amp;token=5f738713-b5a3-4954-b021-352c9d6611da" alt=""><figcaption></figcaption></figure>

## Setting up GitHub PAM Configuration

### Create an GitHub PAM Configuration

Once all the steps above have been taken, add a new PAM Configuration for GitHub Actions

* GitHub ID: a useful name
* Personal Access Token: PAT value from above

<figure><img src="https://762006384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJXOXEifAmpyvNVL1to%2Fuploads%2FZhaFt8ot55NeEDMpOORE%2FScreenshot%202026-10-01%20at%2010.38.33%E2%80%AFAM.png?alt=media&amp;token=515c151f-1351-4a87-822f-e717edd8c124" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.keeper.io/keeperpam/privileged-access-manager/getting-started/pam-configuration/github-actions-environment-setup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.