> For the complete documentation index, see [llms.txt](https://docs.expel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expel.io/workbench-reference/investigations-and-incidents/add-to-an-investigation-or-incident.md).

# Add to an Investigation or Incident

{% hint style="info" %}
Investigations are found at **Activity > Investigations**; Incidents are found at **Activity > Incidents.** 

If you need additional help with locating or viewing, see [View an Investigation](/workbench-reference/investigations-and-incidents/view-an-investigation.md).
{% endhint %}

Any additions or modifications can also be seen by our SOC analysts.

* You can add notes about the Investigation by selecting the **Add Comment** button on the Investigative Actions screen. 
* You can add information to the **Timeline** screen by selecting the **Add Timeline Activity** button. 

You can also select the **Update Investigation** button at the top of the page to view the following screen, where you can perform the additional actions described below.

<div align="left"><figure><img src="/files/G2wuiTNxUyXQTxXDhYBj" alt="An image showing the Edit screen for an investigation."><figcaption></figcaption></figure></div>

These actions include:

1. **Assigning the investigation back to the SOC analysts.** For example:
   * You performed the remediation actions recommended, and want further information from the SOC.
2. **Closing the investigation.** For example:
   * After you review the activity, determine it is benign, and decide no further action needs to be taken.&#x20;
   * The dialog box changes for you to provide a reason to close, and to add notes.
3. **Flagging the investigation as an** [**Incident**](/workbench-reference/investigations-and-incidents/understanding-incidents.md)**.** For example:
   * You review the activity and decide it might be a threat in your environment.
   * The dialog box changes and prompts you for more information about what is going on.
   * If you think this is a critical incident (a security breach may be happening right now), you should provide as much information as you can to help the SOC analysts or your team. The more information you can provide, the better the response is from the SOC analysts or from your team.&#x20;
   * Make sure you assign the incident to Expel if you want the SOC analysts to help. You can still work the incident on your side in the interim.


---

# 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://docs.expel.io/workbench-reference/investigations-and-incidents/add-to-an-investigation-or-incident.md?ask=<question>&goal=<endgoal>
```

`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.