> 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/your-first-30-days/9-validate.md).

# 10: Validate

You completed sections 1-8 and made it through your first 30 days — nice work. Your setup is live, and signals are flowing. Now validate the results, confirm notifications land where they should, and build a weekly rhythm that proves value fast.

## Review Next

<details>

<summary>Dashboards</summary>

When you log in to Material, you land on the Overview Dashboard. This is a great place to begin investigating as it highlights key security insights ready for review or action including. Drill down into any number to open a pre-filled issue search or click any issue title to open the issue detail view.

{% hint style="info" %}
This dashboard data updates on a daily cadence, and reflects activity through the previous day.
{% endhint %}

<figure><img src="/files/2enzuDwxNZJ3rYnanuLB" alt=""><figcaption></figcaption></figure>

**Email Threats Dashboard and Reports**

Everything you configured in step 6, **Enable Email Security** can be tracked in a few ways. From **issues**, click **Email Threats** to narrow the issue list to just email threat related issues:

<figure><img src="/files/GUyM7dGthEqomVVwpBqf" alt=""><figcaption></figcaption></figure>

Then, from the left click **Reports**, then **Email Threats** to open an Email Threat specific report:

<figure><img src="/files/bNwVidmr7o4W7QnMh2yK" alt=""><figcaption></figcaption></figure>

[Learn more here.](/learn-more/risk-areas/email-threats.md)

</details>

<details>

<summary>Explorer</summary>

You've used the Explorer, located in the Material workspace, to create accounts and new tenants in previous deployment steps, and learned how to bulk remediate files. There are a few other functions you can perform in the Explorer:

* Use MQL[^1] and auto-complete to [search for messages](/getting-started/fundamentals/explore/message-search.md) across all enabled mailboxes in real-time and take bulk actions on the results. You can also [search files](/getting-started/fundamentals/explore/file-search.md) by writing custom queries about your Google Drive environment. Open the message/file row to drill into details including headers and routing, related accounts, links, attachments.
  * Use cmd+k or click **All Actions** to download or delete a message, share the message with Material, copy Message ID, etc.

<figure><img src="/files/FE61AhZUSN3MYOICbgQP" alt="moving image of auto complete feature in message search; use drop downs to choose variables and operators to search with"><figcaption><p>Auto-complete feature on the Message Search</p></figcaption></figure>

[Learn more here](#explorer).

</details>

<details>

<summary>Reports</summary>

You've used the Explorer, located in the Material workspace, to create accounts and new tenants in previous deployment steps, and learned how to bulk remediate files. There are a few other functions you can perform in the Explorer:

* Use MQL[^1] and auto-complete to [search for messages](/getting-started/fundamentals/explore/message-search.md) across all enabled mailboxes in real-time and take bulk actions on the results. You can also [search files](/getting-started/fundamentals/explore/file-search.md) by writing custom queries about your Google Drive environment. Open the message/file row to drill into details including headers and routing, related accounts, links, attachments.
  * Use cmd+k or click **All Actions** to download or delete a message, share the message with Material, copy Message ID, etc.

<figure><img src="/files/FE61AhZUSN3MYOICbgQP" alt="moving image of auto complete feature in message search; use drop downs to choose variables and operators to search with"><figcaption><p>Auto-complete feature on the Message Search</p></figcaption></figure>

</details>

<details>

<summary>Saved Views</summary>

Save and reuse your personalized issue list configurations with Saved Views. Create views with specific filters, sorting, grouping, column arrangements, and search queries to quickly access the issues that matter most to your workflow.

[Learn more here.](#saved-views)

</details>

***

## Best Practices

There are a few actions you can take in just 90 minutes per week to start demonstrating value and validate your configuration choices:

#### Email Threat Dashboard - 15 min/week

Glance at total attacks and tactics:

<figure><img src="/files/R9Rn2TJkfuKHTABc9oiK" alt=""><figcaption></figcaption></figure>

* Drill down directly into the numbers to open the related issue filters and investigate.
* Export a PDF to share graphs and visuals with stakeholders.

#### File Search/Custom Detections - 30 min/week

* Run 1-2 high value queries in the Explorer
* Nudge owners of risky files by revising your [file security defaults](/getting-started/deployment-guides/your-first-30-days/7-enable-file-security.md)
* Tune or add a custom detection if needed

#### Message Search - 30 min/week

* Review inbound Email Threat reports
* Run 1-2 queries in the Explorer
* Bulk clean anything suspicious (Learn more in [Fundamentals](/getting-started/fundamentals.md))

#### Event Subscriptions

* Add new notifications as needed and response when they trigger

***

## Up Next

Now that you're done with your initial deployment, give it a little time to run and get used to the output. Review all the [F](/getting-started/fundamentals.md)[undamentals guides](/getting-started/fundamentals.md), then tweak your settings as needed.

[^1]: a querying language unique to Material


---

# 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/your-first-30-days/9-validate.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.