> For the complete documentation index, see [llms.txt](https://docs.material.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.material.security/getting-started/fundamentals/investigate/issue-closure-and-manual-classification.md).
# Issue Closure and Manual Classification
## Issue Closure
* For [state-based issues](#user-content-fn-1)[^1] (e.g. vulnerabilities or misconfigurations), Material automatically detects if the vulnerability is fixed then resolves the issue.
* You, as the analyst, need to close [event-based issues](#user-content-fn-2)[^2] (e.g. notification about unusual behavior). Once you're confident all actions have been taken after investigating them, change the status to **resolved**. (An ignored status also closes the issue/removes it from the active issue count).
## Manual Classification
After reviewing the evidence, you may want to update the classification on an issue to better match your analysis.
**Default Remediation Actions**
When you manually change an issue's classification, Material stages the default remediation for that classification. Click **Save** to apply it.
To configure the default remediation:
1. Click **Settings**
2. Expand **Email Threats**, then click **Issue Triage**.
3. Set remediation per classification just as you would with User Report Auto Classification.
### Mark suspicious or sensitive
From an issue, click **All actions** **(⌘K)** then choose mark suspicious or mark sensitive:
Mark suspicious or mark sensitive from the All actions menu.
[^1]: Identifies potential issues that could lead to future threats. These are ongoing and resolved when a future Material scan shows the risk no longer exists.
[^2]: Identifies a suspicious event that requires further investigation. These detections occur at specific points in time and can be closed once the investigation is complete and the threat
---
# 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.material.security/getting-started/fundamentals/investigate/issue-closure-and-manual-classification.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.
