> 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.md).
# Deployment Guides
Welcome to Material Security!
These guides are your starting point for understanding and deploying Material in your environment. Because adopting Material spans both technical setup and ongoing operational use, we recommend that your IT team and intended admins work through parts of these guides together. This shared understanding helps ensure a smooth deployment and a more effective long-term security program.
## Your First 30 Days
In your first 30 days, you will:
* Connect your tenant so Material can begin detecting and displaying issues right away
* Customize your setup including branding
* Learn to navigate Material
* Automate remediation and response — so Material can take action for you
* Communicate with your org about upcoming changes
Rollout Timeline
How fast you fully deploy is a preference. It's possible to complete most of these guides in one session, however we recommend you consider a few things when choosing how to plan your rollout:
* 👥 **Rollout groups:** Do you want to rollout to everyone at once or take volunteers and test your workflow with a group?
* ⚙️ **Features**: Do you want to configure and enable all features at once or start with one at a time?
* 📢 **Communication**: Will you communicate with your users about everything at once or a feature at a time? For example, how far ahead of implementing a speedbump response do you want your users to be aware that it's coming? They'll need time to adjust to the new workflow and they need to know how to work with it. We have [templates](/getting-started/deployment-guides/communication-templates.md) you can use to help guide you through this.
* 📝 **Internal Change Management Processes**: Are there any internal processes you need to consider when planning your deployment timeline?
All of these considerations can help you design your rollout process and timeline so you can stay on track and inform your stakeholders.
We'll make recommendations along the way — but you can always tweak these to your needs.
---
# 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.md?ask=&goal=
```
`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.