> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/interfacing-help-files-fr/regulatory-compliance/sensitive-events-application/tracking-and-monitoring-sensitive-events.md).

# Tracking & Monitoring Sensitive Events

Sensitive Event List: Browse and manage all reported sensitive events across the organization.

Use the **Sensitive Event List** to view all reported events, whether they are in progress, under investigation, in containment, undergoing corrective action, or resolved.

<figure><img src="https://content.gitbook.com/content/AgpNu7XmgN3Z9B8kIShD/blobs/MNQVjJJjoVXgQsv7gRzn/se-v15-list_v1.png" alt=""><figcaption></figcaption></figure>

***

{% stepper %}
{% step %}

### Filtering Sensitive Events

Use the **Search Panel** to filter the events shown in the grid. You can filter by:

* **Event ID:** Enter the unique identifier for the sensitive event.
* **Nature of the Event:** Select the type of event from the dropdown.
* **Status:** Filter by the current stage of the workflow (e.g., Reported, Under Review, In Containment, Corrective Action, Resolved).
* **Business Division / Line:** Narrow results by the associated division or business line.

{% hint style="info" %}

#### Actions:

* **Filter:** Click to apply your criteria and update the grid with matching results.
* **Clear Filter:** Click to remove all filters and restore the full list of requests.
  {% endhint %}
  {% endstep %}

{% step %}

### Managing Sensitive Events

Use the action buttons in the grid to manage reported events:

* **View** (<i class="fa-eye">:eye:</i>)**:** Open an event in read-only mode. In viewing mode, you can:
  * Review all event details, including investigation, containment, and corrective action history.
  * Download attached files.
  * Access details in supplemental forms or templates.

{% hint style="success" %}
***Tip**: Check the **Current Status** column in the grid to see the event’s stage in the* [*Sensitive Event Management*](/interfacing-help-files/interfacing-help-files-fr/regulatory-compliance/sensitive-events-application/navigating-the-sensitive-events-workflow.md) *workflow.*
{% endhint %}
{% endstep %}
{% endstepper %}

***

### See Also

<table data-view="cards"><thead><tr><th></th></tr></thead><tbody><tr><td>TO DO</td></tr></tbody></table>


---

# 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://interfacing.gitbook.io/interfacing-help-files/interfacing-help-files-fr/regulatory-compliance/sensitive-events-application/tracking-and-monitoring-sensitive-events.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.