> 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/create-corporate-users-single-and-bulk.md).

# Create Corporate Users (Single and Bulk)

This document explains how an account admin can create single or multiple corporate users in a verified domain and then assign account and mailbox permissions.

{% hint style="info" %}
As an account administrator, you can create corporate users in a verified and activated domain.

Before you start, make sure the domain is set up in [How to Add and Manage Domains](/admin-panel/account-settings/how-to-add-and-manage-domains.md).
{% endhint %}

### Create a single corporate user

<figure><img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2F2bZulKaG5bQizq8RzgZQ%2Fimage.png?alt=media&amp;token=004a45a2-f9e0-41f1-b9de-b6241348f2b0" alt="" width="407"><figcaption></figcaption></figure>

1. Open the **Admin panel** and navigate to the **Users** tab.
2. Click the <img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2FfTNiwwGdTRzFMW44zYvz%2Fimage.png?alt=media&amp;token=2aa5b0e2-7960-4b92-b0fc-96358e874499" alt="" data-size="line"> button.
3. Fill in the required fields:

   * **First name**
   * **Last name**
   * email local part (before `@`)
   * domain part (after `@`)

   Optionally, enable personal mailbox creation for the user.
4. Click the <img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2Fd2tg0D1TSgfnpBT8OOVq%2Fimage.png?alt=media&amp;token=18200a0c-127b-44c8-a506-bb6fc5f6796a" alt="" data-size="line"> button.
5. After the user is created, the permissions page opens.
6. Configure permissions:
   * [How to Grant Account Permissions](/admin-panel/users-and-user-roles/how-to-grant-account-permissions.md)
   * [How to Grant Mailbox Permissions](/admin-panel/users-and-user-roles/how-to-grant-mailbox-permissions.md)
7. Click the <img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2FXftzxe3W6Mc40IOZHU9V%2Fimage.png?alt=media&amp;token=79c97277-4569-4d2b-a1f4-76de59abb71d" alt="" data-size="line"> button in the page header to apply the permissions.

If the account has many mailboxes, use search and the permission status filter in the Mailbox tab before assigning mailbox permissions.

{% hint style="info" %}
After you create a user, the system emails them a password setup link. The link is valid for 72 hours (3 days).
{% endhint %}

### Localization settings for corporate users

When a company account creates corporate users, they inherit localization settings from the company account.

Corporate users inherit:

* **Email notifications language**
* **Numbers and date format**

These settings define the default language and regional format used in DocStudio emails and in the recipient interface. For example, if the company account uses Dutch as the **Email notifications language**, new corporate users created in this account receive DocStudio email notifications in Dutch by default.

Corporate users can keep these inherited settings or change them later.

### Bulk creation of corporate users

If you have **Account Owner** role, you can create multiple corporate users at once. To do so:

{% columns %}
{% column %}

1. Click the <img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2FTKi0O6tGS9rL5U7odRPT%2Fimage.png?alt=media&amp;token=5eef6487-70dd-48e8-8d5e-dc5d1461e5ec" alt="" data-size="line"> button in the header and select **Create users**.
2. In the modal window, download the example file for bulk user creation.
3. Open the file in any program that supports `.xlsx`, such as Microsoft Excel or Google Sheets.
4. Save your data in the same `.xlsx` format.
5. Click the <img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2FpRG1sR6tPEABNOYETKXG%2Fimage.png?alt=media&amp;token=ca93e82d-dfa4-4910-a022-ce15269cdcf8" alt="" data-size="line"> button and upload your file.
   {% endcolumn %}

{% column %}

<figure><img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2FVcOB1gcLGA8pD48c8usS%2Fimage.png?alt=media&amp;token=48a66202-2631-4acf-b8f9-f741b1046a22" alt=""><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

{% hint style="info" %}
Do not change the file extension, as the system only accepts `.xlsx` files.
{% 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/create-corporate-users-single-and-bulk.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.
