> 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/deployment-guides/31+-days.md).

# 31+ Days

All Material deployments (regardless of whether you have purchased our [Essentials or Advanced plans](https://material.security/pricing)) share a number of deploy steps. Advanced packages have a few extra steps, noted as "Advanced Only."

{% hint style="info" %}
If you're not sure which package you're deploying, Essentials or Advanced, contact Material Support.

If you bought ATO (Account Takeover) Resilience only, skip to [Deploy Account Takeover Resilience](/getting-started/deployment-guides/deploy-account-takeover-resilience-ator.md).
{% endhint %}

Essential and Advanced Packages are deployed in stages, by capability. You can configure and deploy all these in one sitting, or break it up in a few sessions (see the sample rollout timelines in the [Communication Template scenarios](/getting-started/deployment-guides/communication-templates.md)).

Detections[^1] work as soon as you're finished with the [Pre-Requisites](broken://pages/bIi0N542dSkFjAakdHkS) guide. However, responses, remediation, and protections may not be enabled until you complete the guides in this section.

## How Material Works

{% hint style="success" %}
After you complete deployment, review [Material Fundamentals](/getting-started/fundamentals.md) to learn about the Material workflow and best practices. Share the [Fundamentals](/getting-started/fundamentals.md) guides with any of your teammates who will use Material frequently.
{% endhint %}

At a high level, Material's workflow is broken into three areas that are referenced frequently in these Deployment Guides:

<details>

<summary><strong>Detect</strong></summary>

A [detection](/getting-started/fundamentals/detect.md) is a single rule designed to identify important events or conditions within your Google Workspace or Microsoft 365 environment, which are then surfaced as Issues. At the point in deployment when you are reading this guide, detections are already enabled and working for you.

</details>

<details>

<summary><strong>Investigate</strong></summary>

An [issue](/getting-started/fundamentals/investigate.md) represents a single threat identified by a detection. Issues are created when detection logic matches an entity[^2] in your Google Workspace or Microsoft 365 environment. Using the evidence Material provides, you can make a decision on how to respond.

</details>

<details>

<summary><strong>Response</strong></summary>

[Responses and remediations](/getting-started/fundamentals/respond.md) are the actions you can prescribe or take in Material to respond to and stop any detected threats. There are two ways to fix an issue directly in Material. Depending on the detection type, you can either set a default response, manually set a response, or apply a combination of both responses and remediations.

</details>

[^1]: A **Detection** is a single rule designed to identify important events or conditions within your Google Workspace or Microsoft 365 environment, which are then surfaced as [Issues](/getting-started/fundamentals/investigate.md).

[^2]: an account, file, group, message, or tenant


---

# 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/deployment-guides/31+-days.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.