> 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/communication-templates/staggered-rollout-essentials-or-advanced.md).

# Staggered Rollout: Essentials or Advanced

In this scenario, you'll deploy Material in multiple sessions and communicate with your users along the way.

> **Pros**: Smaller changes to digest, time to identify any end user feedback or problems with overall deployment and improve
>
> **Cons**: Your end users could feel like there are never-ending changes

| Delivery Timing                                                                                                                                     | Template Name                                                                                                                           |
| --------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| 14-30 days prior                                                                                                                                    | <ol><li><a href="#id-1.-introducing-material-security-for-staggered-rollout">Introducing Material Security</a></li></ol>                |
| At [Email Threat response enablement](/getting-started/deployment-guides/your-first-30-days/6-enable-email-remediation/configure-user-reporting.md) | <ol start="2"><li><a href="#id-2.-email-threat-protection-is-deployed-what-to-expect">Email Threat Protection is Deployed</a></li></ol> |
| At [File Data Security response enablement](/getting-started/deployment-guides/your-first-30-days/7-enable-file-security.md)                        | <ol start="3"><li><a href="#id-3.-file-data-security-is-deployed">File Data Security is Deployed</a></li></ol>                          |

{% hint style="success" %}
All templates include customizable content including your organization's name. Be sure to update (or sometimes remove) any inline directions. They're included in brackets and highlighted <mark style="background-color:yellow;">\<like this></mark>.
{% endhint %}

***

## 1. Introducing Material Security

> **Message Purpose:** To inform your users that changes will be coming soon and why
>
> **Delivery Timing:** Material recommends at least 14 days but no more than 30 days in advance of your Go-Live date so users do not forget about it.

<details>

<summary><span data-gb-custom-inline data-tag="emoji" data-code="1f4e9">📩</span> Introducing Material Security template</summary>

**Message Subject:**

Introducing <mark style="background-color:yellow;">**\<your company name>**</mark>’s new information security provider, Material Security—and what it means for you

**Message Body**:

We’re pleased to announce that we’ve partnered with Material Security – an information security company – to protect <mark style="background-color:yellow;">\<your company name></mark> from key security risks. Material keeps connected accounts safe by protecting our company’s fundamental material—our emails, documents, and accounts —before, during, and after a breach.

With Material Security we can:

* Detect sophisticated email based attacks and take action fast through a variety of responses
* Detect potential risks related to files and attachments, including sharing of sensitive data
* Investigate issues quickly and improve our defenses to keep us safe even as attack methods change every day

Please be on the lookout for additional messages as we get closer to deploying Material Security. We’ll send a few emails over the next few weeks as we roll out different features over time. The entire process should take about 1-2 months to complete.

In the meantime, if you want to do a little more research on Material, feel free to take a look at their website here: <https://material.security/>

</details>

***

## 2. Email Threat Protection is Deployed

**Optionally, gather screenshots for your Email Threat Protection is Deployed message:**

> You need four screenshots for this template:
>
> 1. **Screenshot A (User Report Response)**
> 2. **Screenshot B (Banner)**
> 3. **Screenshot C (Block)**
> 4. **Screenshot D (Speedbump)**

**Then, fill out the Email Threat Protection is Deployed template utilizing the screenshots you gathered:**

> **Message Purpose:** To inform your users about what to expect from email threat protection and how to make their own reports
>
> **Delivery Timing:** When you [enable Email Threat responses](/getting-started/deployment-guides/your-first-30-days/6-enable-email-remediation/configure-user-reporting.md)

<details>

<summary><span data-gb-custom-inline data-tag="emoji" data-code="1f4e9">📩</span> Email Threat Protection is Deployed template</summary>

**Message Subject:**

Material Security Email Threat Detection will be on in 7 days – what to expect

**Message Body**:

We recently sent you an email introducing Material Security, our new tool to protect <mark style="background-color:yellow;">**\<Your organization name>**</mark> from email-based attacks. This email includes key information about changes you'll see in one week, and what to do if you have questions.

While many malicious messages will be deleted or moved out of your inbox automatically, others might remain accessible to you, but will look a little different:

* Links and attachments might first open a page asking you to verify you know the sender or simply block access to those links and attachments
* The message might include a banner to draw your attention to something suspicious about the message that you should notice before proceeding.

Examples of these situations are shown below. When you see these, please read them and follow the guidance. If you have questions, you can always reach us at <mark style="background-color:yellow;">**\<contact for the responsible team>.**</mark>

* <mark style="background-color:yellow;">**Screenshot B (Banner)**</mark>
* <mark style="background-color:yellow;">**Screenshot C (Block)**</mark>
* <mark style="background-color:yellow;">**Screenshot D (Speedbump)**</mark>

You also have the power to report suspicious emails that have not been modified as described above or moved to Spam. To do this,

<mark style="background-color:yellow;">**\<alter these options to fit your process:>**</mark>

* Label the email as Suspicious, or
* Forward the email to <mark style="background-color:yellow;">**\<the reporting address you included in Email Threat Settings>**</mark>

\
You’ll get a thank you email in response and updates once we determine if the message is malicious or safe.

* <mark style="background-color:yellow;">**Screenshot A (User Report Response)**</mark>

**Up Next**: We’ll let you know when we officially deploy this functionality in about a week, then shortly after we’ll prepare to deploy File Data Security. You’ll receive a new email highlighting what to expect.

Thank you for your help and cooperation in protecting our organization! Any questions? Let us know here: <mark style="background-color:yellow;">**\<your preferred contact>**</mark>

<br>

</details>

***

## 3. File Data Security is Deployed

**Optionally, gather screenshots for your File Data Security is Deployed message:**

> You need one screenshot for this template:
>
> * **File Issue Response Email**

**Then, fill out the File Data Security is Deployed template utilizing the screenshots you gathered:**

> **Message Purpose:** To inform your users about what to expect from File Date Security and how to open messages safely
>
> **Delivery Timing:** When you [enable File Data Security](/getting-started/deployment-guides/your-first-30-days/7-enable-file-security.md)

<details>

<summary><span data-gb-custom-inline data-tag="emoji" data-code="1f4e9">📩</span> File Data Security is Deployed template</summary>

**Message Subject:**

Google Drive Data Security is enabled – what to expect

**Message Body**:

As you likely know from our previous emails and announcements, we’re slowly rolling out Material Security features to protect our company’s fundamental material—our emails, documents, and accounts —before, during, and after a breach.

Our next rollout is Google Drive Data Security. This feature identifies sensitive content (PII, financial data, legal documents, etc.) archived in your user mailboxes. On your end, you’ll get an email explaining the file issue, and sometimes access to the file will be automatically updated to comply with policy. The email you’ll receive looks something like this:

<mark style="background-color:yellow;">**\<Screenshot: File Issue Response Email>**</mark>

Thank you for your help and cooperation in protecting our organization! This completes our Material Security deployment. Any questions? Let us know here: <<mark style="background-color:yellow;">**your preferred contact>.**</mark>

</details>


---

# 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/getting-started/deployment-guides/communication-templates/staggered-rollout-essentials-or-advanced.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.