# Github Issues Integration

The GitHub Issues integration enables Sprinto to automatically sync issue and project management data from your GitHub organisation. This helps you demonstrate that change management processes are followed and that tickets are created, tracked, and reviewed as part of your compliance requirements.

Once connected, Sprinto can:

* Sync tickets from GitHub Issues.
* Map tickets to relevant controls and checks.
* Continuously monitor change management evidence.
* Auto-update evidence based on ticket activity.

#### Sprinto checks for GitHub Issues integration <a href="#sprinto-checks-for-github-issues-integration" id="sprinto-checks-for-github-issues-integration"></a>

Following are the Sprinto checks available for GitHub Issues integration:

<table><thead><tr><th width="185.12890625">Sprinto check</th><th>Required action</th></tr></thead><tbody><tr><td>No new change management tickets were added in over 30 days</td><td>This check activates when no new change request tickets have been added in the last 30 days.<br> <br>The status remains "Passing" if no new change requests are detected for the configured projects.</td></tr><tr><td>Change management ticket should have an assignee</td><td>This check activates if a change request ticket doesn't have an assigned stakeholder.<br><br>The status is set to "Passing" if a stakeholder is assigned to the change request ticket.</td></tr><tr><td>Ticketing system for change management should be setup</td><td>This check activates if no ticketing system is configured for Change Management.<br><br>The status is set to "Passing" if a ticketing system is configured.</td></tr><tr><td>Ateast one change management system should be connected</td><td><p>This check activates if no change management system is configured in your Sprinto account.</p><p>The status is set to "Passing" if a change management system is configured.</p></td></tr></tbody></table>

### Before you Begin

Ensure the following prerequisites are met:

* You are logged in to the Sprinto Admin Portal.
* You have administrator access to the GitHub organisation you want to connect.
* You have permission to generate personal access tokens (if using a token-based authentication method).
* Your GitHub organisation allows third-party integrations.

***

### Set up GitHub Issues integration

#### Step 1: Navigate to the integration

1. Log in to the Sprinto dashboard.
2. Go to **Settings**.
3. Ensure you are on the **All** tab.
4. In the search bar, type **GitHub Issues**.
5. Click **Connect**.

<figure><img src="https://3220032727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2FMow3xHn5QvPTHt3RTHIb%2FScreenshot%202026-02-11%20at%2015.02.34.png?alt=media&#x26;token=e2a73904-4d50-4747-ba7e-52a4bc526a16" alt="" width="563"><figcaption></figcaption></figure>

***

#### Step 2: Review permissions and data usage

A drawer opens showing:

* Controls and checks that will be automated.
* **Permissions required** (Full access: Read).
* **Data used by Sprinto**, including:
  * Remote ID
  * Name
  * Status
  * Description
  * Collection
  * Assignee
  * Due date
  * Projects
  * Remote created timestamp
  * Remote updated timestamp
  * Users
  * Tickets
  * Tags
  * Ticket type
  * Ticket URL

Review the details and click **Next**.

<figure><img src="https://3220032727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2FvKaxm9kplbBk5s82pfJ4%2FScreenshot%202026-02-11%20at%2015.05.38.png?alt=media&#x26;token=b53362f2-7698-4b51-97fe-3e71564a3aac" alt="" width="375"><figcaption></figcaption></figure>

***

#### Step 3: Confirm setup requirements

In the **Setup GitHub Issues Integration** drawer:

1. Review the setup instructions.
2. Select the checkbox confirming that you have administrator access.
3. Click **Connect to GitHub Issues**.

<figure><img src="https://3220032727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2FzII71X49vmqiec2A4CJJ%2FScreenshot%202026-02-11%20at%2015.06.04.png?alt=media&#x26;token=8d90d63a-3933-4758-bb6d-2557cc93d68b" alt="" width="375"><figcaption></figcaption></figure>

A GitHub authentication pop-up appears.

***

## Authentication methods

You can authenticate using one of the following methods:

1. Fine-grained personal access token (recommended)
2. Personal access token
3. GitHub Issues organisation name

<figure><img src="https://3220032727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2FEHu9tlUdkrdz0ffpsHhX%2FScreenshot%202026-02-11%20at%2015.06.41.png?alt=media&#x26;token=fe285a3a-74e0-442c-8cf5-525f7c927912" alt="" width="295"><figcaption></figcaption></figure>

***

## Method 1: Fine-grained personal access token (Recommended)

#### Step 1: Select authentication type

In the GitHub pop-up:

1. Select **Fine-grained personal access token (recommended)**.

***

#### Step 2: Review access permissions

You will see the read access requested for:

* **Tickets**
* **Users**
* **Collections**

Review the permissions and click **Next**.

<figure><img src="https://3220032727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2FVz4JLjk0JIKjKVhernLg%2FScreenshot%202026-02-11%20at%2015.07.20.png?alt=media&#x26;token=d1b9ee00-5c90-497d-a4a7-ffb0ad1e4b14" alt="" width="293"><figcaption></figcaption></figure>

***

#### Step 3: Enter username and fine-grained token

You will be prompted to enter:

* **GitHub username**
* **Fine-grained personal access token**

To generate a fine-grained personal access token:

* Follow the instructions on this [GitHub page](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#creating-a-fine-grained-personal-access-token).

Ensure the token includes the required read permissions as described in the GitHub guidance.

Enter your:

* Username
* Token (paste it into the Password field)

Click **Next**.

<figure><img src="https://3220032727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2FgcH3CNqzbrXzODQWynhS%2FScreenshot%202026-02-11%20at%2015.09.32.png?alt=media&#x26;token=e1538d1a-e7a8-4b5a-ba91-b171d313a2cc" alt="" width="293"><figcaption></figcaption></figure>

***

#### Step 4: Enter organisation name

You will be prompted to enter your GitHub organisation name.

To find your organisation name:

* Navigate to:\
  \&#xNAN;**\[PLACEHOLDER – GitHub organisation settings URL]**

Copy the organisation name and paste it into the field.

Click **Next**.

The integration will be set up and tickets will begin syncing automatically.

<figure><img src="https://3220032727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2F75pJN3KAuMDV6J4uaQHu%2FScreenshot%202026-02-11%20at%2015.10.25.png?alt=media&#x26;token=fef33357-c039-4a47-9410-921f7174c1c8" alt="" width="299"><figcaption></figcaption></figure>

***

## Method 2: Personal access token

#### Step 1: Select authentication type

In the GitHub pop-up:

1. Select **Personal access token**.

***

#### Step 2: Review access permissions

The read access permissions remain the same:

* Tickets
* Users
* Collections

Click **Next**.

***

#### Step 3: Enter GitHub username and personal access token

You will be prompted to enter:

* **GitHub username**
* **Personal access token**

To generate a personal access token:

* Follow the instructions on this [page](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token).

Ensure the token includes the required permissions, such as:

* Repository access (read)
* Project access (read)
* Webhook permissions (if required)

Enter your:

* Username
* Token

Click **Next**.

<figure><img src="https://3220032727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2FFX6SlfJ9J6kGKaBQvSGk%2FScreenshot%202026-02-11%20at%2015.12.35.png?alt=media&#x26;token=1fba8d09-5630-4817-af7f-6e44e1a03a0b" alt="" width="294"><figcaption></figcaption></figure>

***

#### Step 4: Enter organisation name

Enter the name of the GitHub organisation you want to connect.

To locate your organisation name:

* Refer to:\
  \&#xNAN;**\[PLACEHOLDER – GitHub organisation reference URL]**

Click **Next**.

The integration will be configured successfully.

<figure><img src="https://3220032727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2FEJxQVmEyWzd9d38vrCq8%2FScreenshot%202026-02-11%20at%2015.13.15.png?alt=media&#x26;token=be29ed73-c71a-4ac4-a38b-963590e05d6c" alt="" width="291"><figcaption></figcaption></figure>

***

## Method 3: GitHub Issues organisation name

#### Step 1: Select authentication type

In the GitHub pop-up:

1. Select **GitHub Issues Organisation Name**.

***

#### Step 2: Review access permissions

Review the requested read access for:

* Tickets
* Users
* Collections

Click **Next**.

***

#### Step 3: Enter organisation name

You will be prompted to enter your GitHub organisation name.

Enter the organisation name.\
Once the field is populated, the **Next** button becomes active.

Click **Next** to complete the setup.

<figure><img src="https://3220032727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2FXTnVIjSAXxVQZkprL4y3%2FScreenshot%202026-02-11%20at%2015.15.36.png?alt=media&#x26;token=69244ff7-4ce5-4552-b923-445e18ba4f39" alt="" width="292"><figcaption></figcaption></figure>

***

### What happens after setup

Once the integration is successful:

* Sprinto automatically syncs tickets from GitHub Issues.
* Evidence for mapped controls is updated in real time.
* Change management activities are tracked continuously.
* Relevant checks reflect the latest ticket status.

***

### Troubleshooting

#### The “Next” button is disabled

* Ensure all required fields are populated.
* Verify that the organisation name is entered correctly.
* Confirm that the token has not expired.

***

#### Authentication fails

* Confirm that you have administrator access to the GitHub organisation.
* Verify that the personal access token includes the required permissions.
* Ensure the token has not expired.
* Regenerate the token and try again.

***

#### Tickets are not syncing

* Check that the integration status is **Active** under Settings → Integrations.
* Confirm that the correct organisation name was used.
* Reconnect the integration if required.

***

Kindly get in touch with [Sprinto Support](mailto:www.support@sprinto.com) if you need any assistance with the integration.