2026.10 2026.08 2026.07 2026.06 2026.05 2026.04 2026.02 2026.01
2026.10 2026.08 2026.07 2026.06 2026.05 2026.04 2026.02 2026.01

Configure GitHub Enterprise

The instructions on this page describe how to configure your GitHub Enterprise workspace in preparation for setting up the GitHub Enterprise Beat.

Prerequisites

  • Allow access to your GitHub server addresses over SSL.

  • Ensure that you have a GitHub Enterprise account with an enterprise owner role.

  • Ensure that you have the read:audit_log permission for generating the personal access (classic) token.

Configure the Personal Access Token

Use the following steps to obtain a personal access token in preparation for setting up the GitHub Enterprise beat.

  1. Log in to the GitHub Enterprise owner account.

  2. On your profile page, in the upper right corner, click the profile image, then click Settings.

  3. In the left pane, navigate to Developer Settings.

  4. Under Personal access tokens, click Tokens (classic).

  5. Select Generate new token, and click Generate new token (classic).

  6. Enter a unique Name for your token.

  7. Select the default Expiration option, or enter a custom date.

  8. Assign the scope or token permission read:audit_log for the collector to retrieve events.

For more information, see Scopes for OAuth apps in the GitHub documentation.

  1. Click Generate new token.

  2. Copy the token to a secure location.
    For more information, refer to the Personal Access Token related information in the GitHub documentation.

Once this window is closed, the Token cannot be viewed again.