> 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.md).

# Quick Rollout: Essentials or Advanced

In this scenario, you'll deploy all of Essentials or Advanced in one or a few 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 deployment | 1. [Material Coming Soon](#id-1.-material-coming-soon) |
| 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

**Optionally, gather screenshots for your Material Coming Soon messages**

> You need five 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)**

**Then, fill out the Material Coming Soon 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

<details>

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

**Message Subject:**

Introducing <mark style="background-color:yellow;">**\<your company name>’**</mark>s new information security provider, Material Security— 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 and file workflow that 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>

\
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>

***

## 2. Material is Here

> **Message Purpose:** To inform your users that Material is live and remind them of where to find more information.\
> **Delivery Timing:** At deployment completion, likely when you complete [File Data Security response enablement](/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> Material is Here 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

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.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.