> 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-add-a-corporate-account-admin.md).

# How to Add a Corporate Account Admin

This document explains how to add a corporate account admin by assigning the Account Owner role to acorporate user.

<figure><img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2F9dqVjpJ2eEqCuOAlpgcO%2FAccAdmin.gif?alt=media&amp;token=72891bcc-2342-45e6-9bbf-6f67ba122dd6" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
&#x20;**Corporate Account Admin** — is a user who has access to the company's account, in which a verified and active domain is registered.
{% endhint %}

1. Open the admin panel and navigate to the users tab.
2. Find the required corporate user.
3. Open the user access settings.
4. Click the <img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2FuhJFpoFMqp3kGyd02V3J%2Fimage.png?alt=media&amp;token=286b8f4a-ce00-49aa-a55f-6d6487842ab5" alt="" data-size="line"> button and assign the **Account Owner** role.
5. Save the changes.

The user becomes a corporate account admin and receives full account-level access.

### New Permissions

After you assign the **Account Owner** role, the user can manage:

* Manage account settings
* Invite and manage users
* Grant or revoke user or mailbox permissions
* Manage mailboxes and mailbox access
* Configure security and authentication settings
* Access billing and subscription settings
* Manage integrations, callbacks, and API access
* Configure templates, workflows, and automation settings

{% hint style="warning" %}
**Account Owner** permissions provide full administrative access to the account. Assign this role only to trusted users.
{% endhint %}

#### Related Topics:

* [Create Corporate Users (Single and Bulk)](https://support.docstudio.com/admin-panel/users-and-user-roles/create-corporate-users-single-and-bulk.md)
* [How to Add and Manage Domains](https://support.docstudio.com/admin-panel/account-settings/how-to-add-and-manage-domains.md)
* [Role Management](https://support.docstudio.com/admin-panel/users-and-user-roles/role-management.md)
* [How to Add Users to a Verified Domain](https://support.docstudio.com/admin-panel/users-and-user-roles/how-users-are-added-to-a-verified-domain.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 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-add-a-corporate-account-admin.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.
