> For the complete documentation index, see [llms.txt](https://docs.hivel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hivel.ai/integrations/scm/github/alternate-methods/how-to-integrate-github-with-classic-token.md).

# How to integrate GitHub with Classic Token?

To integrate an additional GitHub account into Hivel, particularly a service account to avoid integrating personal repositories, follow these steps:

***

#### **Step 1: Prepare a Service Account**

1. **Log into the GitHub service account**:
   * Use a dedicated service account that has access to the required repositories for Hivel integration.
   * Avoid using personal GitHub accounts to ensure only the intended repositories are accessed.

***

#### **Step 2: Access Developer Settings**

1. Click on the **Profile Icon** in the top-right corner of the GitHub dashboard.
2. Select **Settings** from the dropdown menu.
3. Scroll down and click on **Developer Settings** in the sidebar.

<figure><img src="/files/lBxWp4bzz7avJyJtSLnC" alt="" width="375"><figcaption><p><br><br></p></figcaption></figure>

<figure><img src="/files/booazMRNy6MpSxkhylvf" alt="" width="563"><figcaption></figcaption></figure>

***

#### **Step 3: Create a Personal Access Token**

1. In **Developer Settings**, navigate to **Personal Access Tokens**.
2. Choose **Tokens (classic).**

<figure><img src="/files/AWfjM0BgjWliePelGUhS" alt=""><figcaption></figcaption></figure>

***

#### **Step 4: Configure the Classic Token**

1. Click **Generate New Token** and select **Classic Token**.
2. Fill out the following details:
   * **Token Name**: Enter `Hivel` as the token name.
   * **Expiration Date**: Set it to **no expiration date** for uninterrupted integration. (You can revoke this token manually when the engagement ends.)
3. Specify the scopes the token needs to operate effectively with Hivel:
   * `repo`

     <figure><img src="/files/FDdQ3dDzuoObR2LTHoLo" alt="" width="563"><figcaption></figcaption></figure>

   * `org`<br>

     <figure><img src="/files/qZD1GHDwAwdVCcSfnd7y" alt="" width="563"><figcaption></figcaption></figure>

   * `hooks`<br>

     <figure><img src="/files/iJqE7b4woPEuLjpIXcRk" alt="" width="563"><figcaption></figcaption></figure>

   * `user`<br>

     <figure><img src="/files/xPneWAkAIBC0xA79Aq3v" alt="" width="563"><figcaption></figcaption></figure>
4. Once the configurations are complete, click **Generate Token**.

***

#### **Step 5: Share the Token with Hivel**

1. **Copy the generated token** immediately, as you won’t be able to view it again.
2. Provide the following details securely to Hivel for the integration:
   * **Personal Access Token**: Paste the copied token.
   * **Username**: Provide the service account’s GitHub username.
   * **Email**: Provide the email associated with the GitHub service account.

***

#### **Step 6: Publish Webhooks**

Ensure that the service account has the required permissions to publish webhooks for your repositories. These permissions are critical for enabling Hivel to fetch and analyze development activity data.