> For the complete documentation index, see [llms.txt](https://docs.mailtrap.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mailtrap.io/account-and-organization/management/manage-your-organization-without-accessing-sub-account-data.md).

# Manage your organization without accessing sub-account data

Organization Access Only lets you delegate organization administration while keeping access to individual sub-accounts separate.

This is especially useful for central operations, finance teams, and agencies or companies managing multiple sub-accounts.

### How to grant Organization Access Only

1. Go to **Organization** → **User Management** → **Add Member**.
2. Leave **Organization & Sub-accounts** unchecked.
3. Select **Organization Access Only** and choose **Admin** or **Viewer**.
4. Send the invitation.

<div align="left" data-with-frame="true"><figure><img src="https://1476453098-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FS3xyr7ba7aGO19rc8dSK%2Fuploads%2FTeH9j9p9avYsHV53JeHb%2FScreenshot%202026-11-17%20at%205.38.51%E2%80%AFPM.png?alt=media&amp;token=a56dbcbd-92a3-4bc4-822d-afd0250ee29e" alt=""><figcaption></figcaption></figure></div>

The recipient joins the organization directly and does not need a sub-account.

For an existing member, edit their permissions in organization-level User Management. To restrict access to the organization, remove Organization & Sub-accounts and any separate sub-account permissions.

If you select Organization & Sub-accounts, Organization Access Only is selected and locked automatically because the broader permission already includes organization access.

Note: This permission is available only in organization-level User Management, not in a sub-account’s user management form. How to choose the right access

| **Permission**                  | **Organization access**                                | **Sub-account access**               |
| ------------------------------- | ------------------------------------------------------ | ------------------------------------ |
| **Organization & Sub-accounts** | Broad organization access, based on the selected level | Access to every sub-account          |
| **Organization Access Only**    | Organization administration or read-only visibility    | No access granted by this permission |
| **Billing**                     | Billing and usage only                                 | No access granted by this permission |

Organization Access Only has two levels: **Admin** and **Viewer**. There is no Owner level.

Keep in mind that **separate permissions still apply**. If a person also has permission to access specific sub-accounts, they can open those sub-accounts. Organization Access Only does not extend that access to any others.

### What Organization Access Only users can do

Those users have access to the Organization panel only (unless they have been granted access to some specific accounts additionally).

<table data-header-hidden data-search="false"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Section of the Organization panel</strong></td><td><strong>Admin</strong></td><td><strong>Viewer</strong></td></tr><tr><td><strong>Sub-accounts</strong></td><td>View the list and create sub-accounts</td><td>View the list</td></tr><tr><td><strong>Usage &#x26; limits</strong></td><td>View usage and edit sub-account limits</td><td>View usage and limits</td></tr><tr><td><strong>Organization details</strong></td><td>View details and rename the organization</td><td>View details</td></tr><tr><td><strong>Billing and subscriptions</strong></td><td>Manage plans, payment methods, and billing settings</td><td>View subscriptions, payment method, and payment history</td></tr><tr><td><strong>User management</strong></td><td>Manage Organization Access Only users and users whose only permission is Billing</td><td>Unavailable</td></tr><tr><td><strong>API Tokens</strong></td><td>Manage organization-only tokens</td><td>Unavailable</td></tr><tr><td><strong>Audit Log</strong></td><td>View organization events when included in the plan</td><td>Unavailable</td></tr></tbody></table>

Neither level grants access to the settings or content inside a sub-account. Creating a sub-account does not give the creator permission to open it.

#### Managing users

An Organization Access Only Admin can invite and manage other Organization Access Only users and users whose only permission is Billing.

They can see organization owners and users with sub-account access, but cannot change those users’ permissions. Furthermore, they cannot change their own access or grant Organization & Sub-accounts access or permissions inside a sub-account.

#### Managing API tokens

Admins can create, reset, and delete tokens with Organization Access Only permissions, at either Admin or Viewer level.

An Admin token can list, create or delete sub-accounts. A Viewer token can only list them. Neither can read or change data inside a sub-account. Billing permission cannot be assigned to API tokens.

### Other management limits

* Transferring a sub-account requires access to that sub-account and is unavailable through this role alone.
* An Organization Access Only Admin can request deletion of a sub-account without access to its contents.&#x20;
* An Organization Access Only Admin can turn off the Organization & Sub-accounts feature from organization settings only when exactly one sub-account remains.


---

# 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://docs.mailtrap.io/account-and-organization/management/manage-your-organization-without-accessing-sub-account-data.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.
