> For the complete documentation index, see [llms.txt](https://support.docstudio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.docstudio.com/admin-panel/users-and-user-roles/how-to-set-up-automatic-mailbox-creation-for-corporate-users.md).
# How to Set Up Automatic Mailbox Creation for Corporate Users
This document explains how to enable automatic mailbox creation for corporate users by assigning a mailbox role.
{% hint style="info" %}
This section will be visible and active only if you have an Account Owner role and your account has at least one verified domain.
{% endhint %}
{% columns %}
{% column %}
1. Enable the toggle switch in the **Mailbox role** section.
2. Enter the mailbox role that will be assigned to corporate users for automatically created mailboxes.
3. Click the button.
A success message appears.
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
{% hint style="info" %}
A corporate account administrator manages the company account in the **Admin panel**. **Corporate Account Admin** — is a user who has access to the company's account, in which a verified and active domain is registered.
{% endhint %}
---
# 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://support.docstudio.com/admin-panel/users-and-user-roles/how-to-set-up-automatic-mailbox-creation-for-corporate-users.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.
button.
A success message appears.
{% endcolumn %}
{% column %}