> 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/user/user-access-and-permissions/access-levels.md).

# Access Levels

This document explains access levels for templates, dictionaries, and scenarios, and what each level allows.

Access level controls who can find and use items like templates, dictionaries, and scenarios.

{% hint style="info" %}
See the [Glossary](https://support.docstudio.com/glossary/glossary.md) for DocStudio term definitions.
{% endhint %}

There are four access levels:

1. **Selected mailboxes** — Accessible by selected mailboxes.
2. **My account** — Accessible by all mailboxes of your account.
3. **Everyone** — Accessible by everyone with the link or the UUID.
4. **Official** — all mailboxes on the platform can find and use the item in the **Official** folder.

{% hint style="info" %}
The **Official** access level can be set only by the system administrator.

If you use a corporate account, a corporate account admin is a user with the **Account Owner** role in a company account with a verified and active domain. Learn more in [How to Add a Corporate Account Admin](https://support.docstudio.com/admin-panel/users-and-user-roles/how-to-add-a-corporate-account-admin.md).
{% 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/user/user-access-and-permissions/access-levels.md?ask=<question>&goal=<user_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.
