> 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/archive/docstudio-structure.md).

# DocStudio Structure

### Overview

<figure><img src="/files/tMpi99P2RXFiDZQ4nfF4" alt=""><figcaption></figcaption></figure>

DocStudio is built around several main concepts:

* **Account** — defines how the user accesses and uses DocStudio.
* **Mailbox** — defines which email address is used for sending envelopes and receiving related notifications.
* **User** — a person who works in DocStudio.
* **Admin** — a user with additional permissions to manage account settings and access.
* **Template** — a reusable setup for creating envelopes faster.
* **Envelope** — a document package sent to recipients for signing, approval, completion, or review.

These concepts work differently in a **Personal Account** and a **Corporate Account.**

Start with [Personal Account](/archive/personal-account.md) or [Corporate Account](/archive/corporate-account.md) if you need details for a specific account type.

### Personal Account

<figure><img src="/files/u11HP0STwntgjhXg8APN" alt=""><figcaption></figcaption></figure>

A **Personal Account** is intended for individual use.

In this account type, one user works with their own documents, templates, envelopes, and mailbox. The user manages their own document flow without company-level access management or shared organization resources.

#### How a Personal Account works

In a Personal Account:

* the account belongs to one user
* the user works with their own documents, templates, and envelopes
* envelopes are sent from the user’s personal mailbox
* completed documents and envelope-related notifications are received by the personal mailbox
* there are no organization members managed by an admin
* access to documents and envelopes is controlled by the account owner

#### Mailbox in a Personal Account

In a Personal Account, the mailbox belongs to one user.

It is used to:

* send envelopes
* receive envelope-related notifications
* receive completed documents

The mailbox is not shared with other users.

### Corporate Account

<figure><img src="/files/gYwTRetrp8Wd9urrLOir" alt=""><figcaption></figcaption></figure>

A **Corporate Account** is intended for companies, teams, departments, or organizations.

In this account type, multiple users can work within the same corporate environment. Access to templates, envelopes, mailboxes, and account settings may depend on user roles and permissions.

#### How a Corporate Account works

In a Corporate Account:

* the account belongs to a company or organization
* admins can invite and manage multiple users
* users may have different roles and permissions
* admins can manage users, access, and account settings
* users may work with shared company resources
* envelopes can be sent from corporate mailboxes
* mailbox access depends on permissions

#### Mailbox in a Corporate Account

In a Corporate Account, mailboxes can be used as company or team email identities.

They can be used to:

* send envelopes on behalf of a company, team, or department
* receive envelope-related notifications
* receive completed documents
* separate business communication from a user’s personal mailbox
* allow authorized users to send envelopes from shared mailboxes

A user can use only the mailboxes they have access to.

### Personal Account vs Corporate Account

<figure><img src="/files/f2APaUs8FgVk8vRLmf5Q" alt=""><figcaption></figcaption></figure>

### Key Concepts

#### Account

An **Account** defines how a user accesses DocStudio and what functionality is available.

There are two main account types:

* **Personal Account**
* **Corporate Account**

The account type defines what the user can manage, which mailbox they can use, and whether they work independently or as part of an organization.

See [Personal Account](/archive/personal-account.md) and [Corporate Account](/archive/corporate-account.md) for details.

#### Mailbox

A **Mailbox** is an email identity used to send envelopes and receive related notifications.

A mailbox can be used to:

* send envelopes
* receive envelope notifications
* manage document communication between the sender and recipients

See [How to Set a Default Mailbox](/user/mailbox/mailbox-user/how-to-set-a-default-mailbox.md), [How to Control Mailbox Visibility](/user/mailbox/mailbox-user/how-to-control-mailbox-visibility.md), and [How to Find a Mailbox ID (UUID)](/user/mailbox/mailbox-user/how-to-find-a-mailbox-id-uuid.md) for common mailbox actions.

#### User

A user is a person who has access to a DocStudio account.

A user may be able to:

* create envelopes
* send envelopes to recipients
* sign or complete documents
* approve or review documents
* create and use templates
* access specific mailboxes
* manage documents and envelope flows

See [Personal Settings Page Overview](/user/user-profile/personal-settings-page-overview.md), [How to Change Your Password](/user/user-profile/how-to-change-your-password.md), and [How to Delete a Profile](/user/user-profile/how-to-delete-a-profile.md) for user-level actions.

#### Corporate Account Admin

An **Account Admin** is a user with additional management permissions in a Corporate Account.

An admin may be able to:

* invite and manage users
* configure access permissions
* manage corporate mailboxes
* update account or organization settings

Admin functionality is not available in a Personal Account because there are no organization members or shared corporate resources to manage.

See [How to Add a Corporate Account Admin](/admin-panel/users-and-user-roles/how-to-add-a-corporate-account-admin.md) to learn more.

#### Envelope

An **Envelope** is a package that contains one or more documents sent to recipients for action.

An envelope may include:

* documents
* recipients
* recipient roles
* fields to complete or sign
* message or subject
* signing or approval flow
* sending mailbox
* envelope status

Recipients may be asked to sign, approve, complete, review, or receive documents depending on their assigned role.

See [How to Create and Send an Envelope](/user/envelopes/how-to-create-and-send-an-envelope.md) for the full workflow.

#### Template

A **Template** is a reusable setup that helps users create envelopes faster.

A template can include predefined:

* documents
* dynamic fields
* recipient roles
* signing or approval flow
* settings used during envelope creation

Templates help standardize document processes and reduce the time needed to prepare envelopes.

See [How to Create and Configure a Template](/user/template-builder/template/how-to-create-and-configure-a-template.md) for setup details.

### Related pages

* [Getting Started](/user/getting-started.md)
* [Personal Account](/archive/personal-account.md)
* [Corporate Account](/archive/corporate-account.md)


---

# 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://support.docstudio.com/archive/docstudio-structure.md?ask=<question>&goal=<endgoal>
```

`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.
