> 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/respond/configure-default-responses.md). # Configure Default Responses When you set a response at the detection level, any issue created by this detection will follow the same workflow unless you change the response at the issue level. Default fixes can be set for many detections, but not all. Some responses must be [manually set individually at the issue level](/getting-started/fundamentals/respond/respond-to-an-issue-manually.md), while other responses can only be set as default detection responses. ## Set default responses To configure a detection's default response, open the [Detection detail view](/getting-started/fundamentals/detect.md#detection-detail-view). Then add your response preferences. {% hint style="info" %} Not all detections allow for default responses; [set responses individually at the issue level for those](/getting-started/fundamentals/respond/respond-to-an-issue-manually.md). {% endhint %}

The response workflow **begins when the event or state is triggered**. If you edit the default response in the detection, it applies to any issues going forward (but doesn't apply retroactively). There are four standard response options you can choose from. You can use each response option once in your default workflow. Some detections have additional response issues based on their detection logic. ### Email Notification

Send an email notification any time the detection creates a new issue. You can specify which email or group based on the file location: a user's or a shared drive. The email address must exist in Material. A default custom message is located in the email notification option, but you can alter it as needed. Click the variables to insert personalized text (rendered in the email). ### Grace Period

Use Grace Periods to give users time to self-remediate, or to allow you time to manually create a response or analyze. Grace periods can't be the first step in your response flow. ### Update Permissions

Tightening permissions on a file involved in an issue can be an effective remediation. Toggle the options on and choose your desired roles based on Google or Microsoft 365 parameters. ### Update Labels

You can add or remove Google labels automatically as part of your fix workflow. --- # 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/respond/configure-default-responses.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.