> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/data-library/incidents/dashboard-actions/add-and-manage-incident-sources.md).

# Add and Manage Incident Sources

Sprinto allows you to integrate a wide range of incident management systems (IMS) to centralise incident visibility and response. These sources can include internal platforms like Sprinto itself or external tools such as PagerDuty, Jira, Microsoft Defender, and more.

Once integrated, Sprinto fetches incident tickets automatically or enables employees to report issues manually. Each added system is displayed as a dedicated tab under the *Incidents* section for easy access and resolution tracking.

***

### Add a New Incident Source

Here's a short video on How to manage Incidents with external systems.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2FAjKkwfETRs8stcuwMkmv%2FManaging%20Incidents%20with%20External%20Systems.mp4?alt=media&token=791d5057-6c7d-4e69-b1d6-f6f0bb86fda4>" %}

1. Go to **Data Library > Incidents > Overview**.
2. Click **Add system**.
3. From the list of available tools, choose the incident management system you want to integrate (e.g. GuardDuty, OpsGenie, Jira).
4. Follow the on-screen instructions to connect the tool and grant access permissions.
5. Once added, the system appears as a new tab in the Incidents section.

{% hint style="info" %}
For tools like GuardDuty and Microsoft Defender, ensure that API permissions are correctly set up to enable ticket sync.
{% endhint %}

***

### Manage Incidents with Sprinto

Here's a short video on how to manage Incidents with Sprinto.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2FCjIur33nL3VHxtWcIftN%2FManaging%20Incidents%20with%20Sprinto.mp4?alt=media&token=c08e696c-369a-48fd-8f31-c777d5b3182d>" %}

***

### Configure Connected Services

After integration, you can configure which services within that system Sprinto should monitor.

1. In the *Overview* tab, click **Manage** next to the integrated system (e.g. PagerDuty).
2. Select the services to monitor (e.g. `bank payment process`, `test-service`).
3. Click **Continue** to confirm.
4. Set up optional email-based incident reporting if applicable (see below).

{% hint style="info" %}
**Example**: For PagerDuty, Sprinto supports email-based reporting. Add a valid email (e.g. `nadeem@sprinto.com`) linked to your PagerDuty inbox.
{% endhint %}

***

### Set Up Employee Reporting via Email

This step is applicable only for systems like PagerDuty that support email-to-ticket functionality.

1. In the system configuration drawer (e.g. **Manage PagerDuty**), enter the designated incident-reporting email address.
2. Ensure this address is linked to your PagerDuty account.
3. Click **Save Changes**.

Employees can now report incidents by sending an email to this address. Tickets are created automatically in PagerDuty, and Sprinto fetches them for compliance monitoring.

***

### View and Fix Integration Errors

If Sprinto detects an issue with any connected system:

* An alert appears in the Overview tab (e.g. *Issue detected in Freshservice*).
* Click **View and Fix** to go to the Integrations page and resolve the error.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sprinto.com/data-library/incidents/dashboard-actions/add-and-manage-incident-sources.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
