> 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/quick-rollout-essentials-or-advanced-+-ato-resilience.md).

# Quick Rollout: Essentials or Advanced + ATO Resilience

{% hint style="info" %}
If you only purchased Account Takeover (ATO) Resilience as a stand-alone, use the [ATO Resilience Templates](/getting-started/deployment-guides/communication-templates/staggered-rollout-ato-resilience.md) instead.
{% endhint %}

In this scenario, you'll deploy all of Essentials or Advanced in one or just a couple of sessions.

> **Pros**: Fewer comms, one moment of change for your end users to digest
>
> **Cons**: Too much change can lead to end users not understanding all the changes because there is too much to process at once

| Timing                                                                                                                                                          | Template Name                                                                           |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| 7 days prior to [enabling Email Threat responses](/getting-started/deployment-guides/your-first-30-days/6-enable-email-remediation/configure-user-reporting.md) | 1. [Material Coming Soon + ATO Resilience](#id-1.-material-coming-soon--ato-resilience) |
| Deployment completion                                                                                                                                           | 2. [Material is Here](#id-2.-material-is-here)                                          |

{% 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. Material Coming Soon + ATO Resilience

**Optionally, gather screenshots for your Material Coming Soon + ATO Resilience message:**

> You need seven screenshots for this template:
>
> 1. **Screenshot A (User Report Response)**
> 2. **Screenshot B (Banner)**
> 3. **Screenshot C (Block)**
> 4. **Screenshot D (Speedbump)**
> 5. **Screenshot E** **(File Issue Response Email)**
> 6. **Screenshot F (Account Verification)**
> 7. **Screenshot G (Redacted email)**

**Then, fill out the Material Coming Soon + ATO Resilience template utilizing the screenshots you gathered:**

> **Message Purpose:** To inform your users about why you’re making changes and what to expect
>
> **Delivery Timing:** 7 days prior to deployment

{% hint style="info" %}
We also have interactive tutorials about resetting passwords and unlocking emails that you can include in your communication [here](/getting-started/deployment-guides/communication-templates/tutorials-for-end-users.md).
{% endhint %}

<details>

<summary>Material Coming Soon + ATO Resilience 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.

This email outlines a number of changes to your email inbox, files, and password reset process you'll see soon:

**Email Updates:**

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;">**Include**</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 needs>**</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>

**Google Drive Updates:&#x20;**<mark style="background-color:yellow;">**\<omit if you don't use Google drive>**</mark>

Google Drive Data Security 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 E: (File Issue Response Email)**</mark>

**Password Resets:**

When you reset a password via email, you will first receive a verification email from Material. It looks something like this:

<mark style="background-color:yellow;">**\<Screenshot F: Account Verification>**</mark>

* Follow the instructions in the email to verify your identity using <mark style="background-color:yellow;">**\<mfa provider>**</mark>. Once your identity is verified, the original password reset email will be delivered to your inbox. This quick check with <mark style="background-color:yellow;">**\<mfa provider>**</mark> allows us to make sure the verification message lands in the right hands.
* If you did not request a password reset, click **I did not request to reset my account**.

**Sensitive Emails:**

Material scans for content like credit card numbers or personally identifiable information in your email, then categorizes them as sensitive and redacts them for security. You can then access them via a seamless retrieval flow.

Every protected email is replaced with stub, showing you message properties and a link to retrieval the full message:

<mark style="background-color:yellow;">**\<Screenshot G: Email Redaction>**</mark>

<mark style="background-color:yellow;">\*\*\*\*\*\*\*</mark>

<mark style="background-color:yellow;">**\<Variant A below: Google Drive instructions (delete if using Microsoft)>**</mark>

To access the message, **click the link in the email and then complete the authentication steps** just like you normally do when signing in. Once you authenticate, this message will be put back in your **inbox** for <mark style="background-color:yellow;">**\<your default retrieval grace period time>**</mark>. After that time has passed, you will need to authenticate again when prompted.

Once you retrieve one redacted email, you have **\<your default retrieval challenge session time>** to open other redacted emails without authenticating.

<mark style="background-color:yellow;">\*\*\*\*\*\*\*</mark>

<mark style="background-color:yellow;">**\<Variant B below: Microsoft instructions (delete if using Google Drive)>**</mark>

To access the message, **click the link in the email and then complete the authentication steps** just like you normally do when signing in. Once you authenticate, this message will be put back in your **Retrieved Items folder** for <mark style="background-color:yellow;">**\<your default retrieval grace period time>**</mark>. After that time has passed, you will need to authenticate again when prompted.

Once you retrieve one redacted email, you have **\<your default retrieval challenge session time>** to open other redacted emails without authenticating.

<mark style="background-color:yellow;">\*\*\*\*\*\*\*</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>

***

## 2. Material is Here

> **Message Purpose:** To inform your users that changes will be coming soon and why
>
> **Delivery Timing:** At deployment completion, likely when you complete [Identity Protection ](/getting-started/deployment-guides/deploy-account-takeover-resilience-ator/enable-identity-protection.md)deployment

<details>

<summary>Material is Here + ATO Resilience template</summary>

**Message Subject**:

<mark style="background-color:yellow;">**\<Your company name>**</mark>’s new information security provider, Material Security, is now live!

**Message Body:**

We’re pleased to announce that we finished deploying 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
* Protect sensitive information and related accounts in the event of a breach

Please refer to last week's email with directions on what to expect in your inbox <mark style="background-color:yellow;">and with your Google Drive workflow</mark>.

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

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>

</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/quick-rollout-essentials-or-advanced-+-ato-resilience.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.