> For the complete documentation index, see [llms.txt](https://docs.n8n.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.n8n.io/administer/manage-users-and-access/understand-account-types.md).

# Understand account types

There are three account types: owner, admin, and member. The account type affects the user permissions and access.

{% hint style="info" %}
**Feature availability**

To use admin accounts, you need a pro or enterprise plan.
{% endhint %}

{% hint style="info" %}
**Account types and role types**

Account types and role types are different things. Role types are part of [RBAC](/administer/manage-users-and-access/set-permissions-and-roles-rbac.md).

Every account has one type. The account can have different [role types](/administer/manage-users-and-access/set-permissions-and-roles-rbac/see-available-roles.md) for different [projects](/administer/manage-users-and-access/set-permissions-and-roles-rbac/organize-work-in-projects.md).
{% endhint %}

{% hint style="info" %}
**Create a member-level account for the owner**

n8n recommends that owners create a member-level account for themselves. Owners can see and edit all workflows, credentials, and projects. However, there is no way to see who created a particular workflow, so there is a risk of overriding other people's work if you build and edit workflows as an owner.
{% endhint %}

| Permission                                                                                                         | Owner | Admin | Member |
| ------------------------------------------------------------------------------------------------------------------ | ----- | ----- | ------ |
| Manage own email and password                                                                                      | ✅     | ✅     | ✅      |
| Manage own workflows                                                                                               | ✅     | ✅     | ✅      |
| View, create, and use tags                                                                                         | ✅     | ✅     | ✅      |
| Delete tags                                                                                                        | ✅     | ✅     | ❌      |
| View and share all workflows                                                                                       | ✅     | ✅     | ❌      |
| View, edit, and share all credentials                                                                              | ✅     | ✅     | ❌      |
| Set up and use [Source control](/administer/use-source-control-and-environments.md)                                | ✅     | ✅     | ❌      |
| Create [projects](/administer/manage-users-and-access/set-permissions-and-roles-rbac/organize-work-in-projects.md) | ✅     | ✅     | ❌      |
| View all projects                                                                                                  | ✅     | ✅     | ❌      |
| Add and remove users                                                                                               | ✅     | ✅     | ❌      |
| Access the Cloud dashboard                                                                                         | ✅     | ❌     | ❌      |


---

# 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://docs.n8n.io/administer/manage-users-and-access/understand-account-types.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.