> 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/jp/privileged-access-manager/getting-started/pam-configuration/github-actions-environment-setup.md).

# GitHub Actions環境のセットアップ

KeeperPAM用GitHub環境の構成

## GitHub環境の概要 <a href="#iam-admin-user" id="iam-admin-user"></a>

{% hint style="info" %}
ボルトUIはバージョン18.8で更新される予定です。
{% endhint %}

GitHubのシークレットは、PAM構成レコードで指定したトークンを使用してKeeperゲートウェイが管理できます。本ガイドでは、GitHubテナント向けPAM構成の設定手順を取り扱います。

**注**: 現時点では、GitHub PAMはユニバーサルシークレット同期にのみ使用できます。

### 要件 <a href="#prerequisites" id="prerequisites"></a>

1. 本ガイドに進む前に、[Keeperゲートウェイのインストールと構成](/keeperpam/jp/privileged-access-manager/getting-started/gateways/one-time-access-token.md)が完了していることを確認してください。
2. 必要なシークレットアクセス権を持つ、きめ細かなパーソナルアクセストークンを作成します。たとえば、以下の権限が必要です。
   * 組織のシークレットへの読み取り/書き込みアクセス権
   * リポジトリメタデータへの読み取りアクセス権
   * リポジトリエージェントシークレットへの読み取り/書き込みアクセス権

APIキーの作成については、[GitHubのドキュメント](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens)をご参照ください。

## GitHub PAM構成のセットアップ <a href="#setting-up-github-pam-configuration" id="setting-up-github-pam-configuration"></a>

### GitHub PAM構成の作成 <a href="#create-an-github-pam-configuration" id="create-an-github-pam-configuration"></a>

上記の手順がすべて完了したら、GitHub Actions向けの新しいPAM構成を追加します。

* GitHub ID: わかりやすい名前
* Personal Access Token: 上記で作成したPATの値


---

# 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/jp/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.