> 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/user-report-structure.md).
# ​User Report Structure
This document explains which sheets are included in the user report file and what data each sheet contains.
{% columns %}
{% column %}
1. The first sheet is **Roles**. It lists all roles available in the account.
To check what a role allows, use the UI or the API. You can also refer to the **Account** and **Mailbox** sheets.
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
{% columns %}
{% column %}
2\. The second sheet is **Permissions**. It lists permissions available for the account and for mailboxes.
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
{% columns %}
{% column %}
3\. The third sheet is **Users**. Use it to fill in user details:
* first name
* last name
* email
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
You can also choose whether to create a personal mailbox for each user. Enter `Y` or `N` or leave it blank.
Users can be created only for verified domains. If you add users from an unverified or inactive domain, the entire user creation process stops.
{% columns %}
{% column %}
4\. The fourth sheet is **Account**. Use it to set account access for specific users from the **Users** sheet.
You can grant access using roles or individual permissions. If the email address is incorrect, the user is not added to the platform.
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
{% columns %}
{% column %}
5\. The fifth and following sheets are **Mailboxes**. Each sheet has the mailbox ID at the top.
Use these sheets to grant mailbox access through roles or individual permissions. If the email address is incorrect, the user is not added to the platform.
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
After you fill in the file, upload it to create the users. Users receive emails with instructions to set up their access.
---
# 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/user-report-structure.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.
