> For the complete documentation index, see [llms.txt](https://docs.couchdrop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.couchdrop.io/administration/user-and-group-management/user-roles.md).

# User Roles

Learn how Couchdrop uses roles to control how users access and manage your account.

## Overview

Couchdrop uses a small number of roles to control what users can access and manage.

There are four roles:

<table><thead><tr><th width="169.9921875">Role</th><th>What they can do</th></tr></thead><tbody><tr><td><strong>Owner</strong></td><td>Has access to all Couchdrop functionality and account settings, including billing and advanced security settings. Each Couchdrop account has one Owner.</td></tr><tr><td><strong>Administrator</strong></td><td>Can access the <a href="/administration/admin-panel-and-user-mode.md"><strong>Admin Panel</strong></a> and manage users, groups, settings, and permissions, excluding Owner-only functionality. Use this role for people who need to administer the Couchdrop account and team members.</td></tr><tr><td><strong>Team Member</strong></td><td>Can use Couchdrop operational features without access to the <strong>Admin Panel</strong>. Team Members are useful when someone needs to perform tasks such as creating External Users, Mailboxes, Shared Links, or Automations without access to billing, security settings, or other account administration. Their access to individual features can be controlled through <a href="/administration/permissions.md">permissions</a>.</td></tr><tr><td><strong>External User</strong></td><td>A restricted account for a customer, partner, application, or automated system. External Users can be given access to specific folders and connection methods such as SFTP, FTP, or the Web Portal without access to Couchdrop administration.</td></tr></tbody></table>

A role is selected when a user is created and can be changed later.

## Internal and External Users

Couchdrop users fall into two broader user types.

### Internal Users

**Owners, Administrators, and Team Members** are Internal Users.

Internal Users are people within your organization who either administer Couchdrop or use its operational features.

The distinction between the roles is primarily how much account-level access they have:

* **Owners** have full account access.
* **Administrators** can manage the Couchdrop account through the Admin Panel.
* **Team Members** can work with permitted Couchdrop features without access to the Admin Panel.

For example, you might give a support or operations user the **Team Member** role so they can create and manage External Users, including SFTP users, without giving them access to billing or administrative settings.

{% hint style="info" %}
Internal Users are managed from **Administration > Users**. Managing Internal Users requires the **Owner** or **Administrator** role.
{% endhint %}

### External Users

**External Users** are accounts normally created for customers, partners, applications, and automated systems that need to send or receive files.

They can be restricted to specific folders and connection methods without being given administrative access.

For example, an External User might be created for a business partner that needs to upload files over SFTP to a specific folder.

{% hint style="info" %}
External Users can be managed from **SFTP & FTPs Users** in User Mode by users with the appropriate permissions, or from **Administration > Users** by an Owner or Administrator.
{% endhint %}

## Feature access

A role determines a user's overall level of access. Permissions determine which individual Couchdrop features they can use.

Feature access can be configured at three levels:

<table><thead><tr><th width="118.5859375">Level</th><th>Configuration location</th><th>Description</th></tr></thead><tbody><tr><td><strong>Account</strong></td><td><strong>Administration > Security Settings</strong></td><td>Sets default feature access across the Couchdrop account.</td></tr><tr><td><strong>Group</strong></td><td><strong>Administration > Groups</strong></td><td>Applies feature access to members of a group.</td></tr><tr><td><strong>User</strong></td><td><strong>Administration > Users</strong></td><td>Applies feature access to an individual user.</td></tr></tbody></table>

This is particularly useful for Team Members.

For example, two users can both have the **Team Member** role while one is allowed to create External Users and Mailboxes, while the other can only work with Shared Links.

Their role remains the same, but their feature permissions determine what they can actually do.

{% hint style="info" %}

#### Grant operational access without Admin permissions

Users who need to create folders, manage Automations and Actions, and create SFTP users should be assigned the Team Member/Manager role. This provides the required operational access without exposing billing, internal-user management, or other administrative settings.
{% 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://docs.couchdrop.io/administration/user-and-group-management/user-roles.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.
