> 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/regulatory-compliance/sensitive-events-application/navigating-the-sensitive-events-workflow/containment-of-the-sensitive-event.md).
# Containment of the Sensitive Event
Document immediate containment measures and determine whether the event requires further investigation or can be finalized.
When a sensitive event is submitted for **immediate containment**, the assigned owner receives a notification in their **Pending Tasks**, prompting them to address and rectify the issue.
Clicking on the subject in **Pending Tasks** or the button in the email opens the **Containment of the Sensitive Event** form. This form allows users to review the event details, document containment actions, and decide whether to close the event or return it for further investigation.
***
{% stepper %}
{% step %}
### Document Immediate Containment Measures
* **Provide a Detailed Description of the Containment/Correction:**\
A rich text field used to describe the steps taken to immediately contain or correct the issue.
* **Containment Evidence:**\
Upload supporting documentation or files that validate the containment or correction activities.
{% endstep %}
{% step %}
### Discussion & Collaboration
* **Comment(s):**\
Allows users to provide notes or feedback on the event and its containment. This section functions like a discussion board, enabling collaborative communication among stakeholders.
* Users can edit or delete their own comments.
* Users can reply to comments left by others.
{% endstep %}
{% step %}
### Return for Investigation or Finalize Containment
At the bottom of the form, users can select one of the following actions:
* **More Details Needed, Send Back to Investigator:**\
Returns the report to the investigator for additional details or further action. The designated investigator will resume responsibility for continuing the investigation.
* **Issue Contained:**\
Confirms that the issue has been effectively contained. The designated reviewer will receive a task to sign off on the event resolution.
{% endstep %}
{% endstepper %}
***
---
# 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, and the optional `goal` query parameter:
```
GET https://interfacing.gitbook.io/interfacing-help-files/regulatory-compliance/sensitive-events-application/navigating-the-sensitive-events-workflow/containment-of-the-sensitive-event.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
