> 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/working-with-issues/respond.md).

# Respond

**Responses (remediations)** are the actions you can prescribe or take in Material to protect entities from any detected threats.

These steps are either:

* Programmatic events that can be run directly from the Material UI as [default responses](/working-with-issues/respond/configure-default-responses.md)
* Manual responses created at the issue level
* Actions that need to be taken outside of Material (i.e. updating Google workspace rules)

There are two ways to respond to an issue directly in Material. Depending on the detection type, you can either set a default response, manually set responses, or apply a combination of both.

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Default Response</strong></td><td>Automatically protect issues based on the detection type</td><td></td><td><a href="/working-with-issues/respond/configure-default-responses.md">Configure Default Auto-Responses</a></td></tr><tr><td><strong>Issue Responses</strong></td><td></td><td>Manually respond to an issue, on top of or replacing a default response</td><td><a href="/working-with-issues/respond/respond-to-an-issue-manually.md">Respond to an Issue Manually</a></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://docs.material.security/working-with-issues/respond.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.
