> 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/deployment-wrap-up.md).
# Deployment Wrap Up
By now, you should have completed all the steps in the [Pre-Requisites](broken://pages/bIi0N542dSkFjAakdHkS) and [Deploy Essentials or Advanced](/getting-started/deployment-guides/31+-days.md) Guides or the [Deploy Account Takeover Resilience](/getting-started/deployment-guides/deploy-account-takeover-resilience-ator.md) Guide. Scan through this high-level task list to double check you've done it all:
* [Assigned admin roles, individual and group roles](/getting-started/deployment-guides/your-first-30-days/3-assign-additional-roles-optional.md)
* [Set up SSO](/getting-started/deployment-guides/your-first-30-days/4-configure-sso-optional.md)
* [Enabled Email Threat Protection](/getting-started/deployment-guides/your-first-30-days/6-enable-email-remediation/configure-user-reporting.md)
* [Configured Email Redaction and reviewed its reports](/getting-started/deployment-guides/your-first-30-days/6-enable-email-remediation.md)
* [Configured Google Drive Security and enabled response and remediation](/getting-started/deployment-guides/your-first-30-days/7-enable-file-security.md)
Additionally, if you purchased ATO Resilience (either as an add-on or stand-alone) you should have:
* [Set Email Redaction grace periods](/getting-started/deployment-guides/deploy-account-takeover-resilience-ator/enable-email-redaction.md)
* [Enabled Email Identity Protection including server-side routing](/getting-started/deployment-guides/deploy-account-takeover-resilience-ator/enable-identity-protection.md)
:envelope: Be sure you communicated about the changes and what your users can expect in their workflows now. See [Communication Templates](/getting-started/deployment-guides/communication-templates.md) for help there if you haven't already informed then or you need to send a refresher.
Completed all of the above? :tada: **Congrats! You're fully deployed.**
:track\_next: Next, explore the [Working with Issues](/working-with-issues/investigate.md) guides and share them with other Material admins to fully leverage Material in your strategy.
## Feedback
Please let us know if these Deployment Guides were helpful and add any feedback by **rating it on the top right**, under the table of contents.
Rate under the table of contents
---
# 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/deployment-wrap-up.md?ask=&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.
