> 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/admin-panel-and-user-mode.md).

# Admin Panel and User Mode

## Overview

Couchdrop has two main areas: **User Mode** and the **Admin Panel**.

They serve different purposes:

* **User Mode** is where users work with files, transfer workflows, and the services available to them.
* **Admin Panel** is where administrators configure and govern the Couchdrop account.

### User Mode

User Mode is the day-to-day workspace in Couchdrop.

It is where users access the files, transfers, workflows, and services they have permission to use.

Depending on the user's permissions, User Mode can include:

* **File Browser**, **Run Actions**, and **Tasks**
* **SFTP & FTPS Users**
* **Automations**
* **Mailboxes**
* **Webhooks**
* **AS2 Stations**
* **Shared Links** and **Request Files**
* **Integrations**
* **B2B Connect**
* **Marketplace**

{% hint style="warning" %}
Not every user will see every option. What appears in User Mode depends on the permissions and features assigned to that user.
{% endhint %}

#### Who can access User Mode

All Couchdrop user types can potentially use User Mode:

* **Owners** can access User Mode and the Admin Panel.
* **Administrators** can access User Mode and the Admin Panel.
* **Team Members** can access User Mode only.
* **External Users** can access User Mode **only when they have been granted**[ **Web Portal access**](/file-sharing/web-portal-access.md).

Team Members are particularly useful when someone needs to work with operational features without access to account administration.

For example, a Team Member can create and manage External Users such as SFTP users, while remaining unable to access billing, security settings, or other administrative configuration.

### Admin Panel

The Admin Panel is the account-wide management area in Couchdrop.

It is used to configure and govern the Couchdrop account, including areas such as:

* Users and groups
* Permissions
* Connections and integrations
* Security settings
* Reporting and activity
* Other account-level configuration

Use the Admin Panel when you need to make changes that affect the Couchdrop account rather than carry out day-to-day transfer work.

#### Who can access the Admin Panel

Only users with administrative roles can access the Admin Panel:

* **Owner**
* **Administrator**

**Team Members cannot access the Admin Panel.**

**External Users cannot access the Admin Panel.**

## Switching between User Mode and Admin Panel

Owners and Administrators can switch between **User Mode** and the **Admin Panel** using the switch in the top-right of the navigation bar.

Users without administrative access only see User Mode.

## User Mode vs. Admin Panel

<table><thead><tr><th width="148.65234375">Area</th><th>Purpose</th><th>Who can access it</th></tr></thead><tbody><tr><td><strong>User Mode</strong></td><td>Work with files, transfers, workflows, and operational features</td><td>Owner, Administrator, Team Member, and External User with Web Portal access</td></tr><tr><td><strong>Admin Panel</strong></td><td>Configure and govern the Couchdrop account</td><td>Owner and Administrator only</td></tr></tbody></table>

A useful way to think about the distinction is:

**User Mode is for operating Couchdrop. Admin Panel is for administering Couchdrop.**


---

# 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/admin-panel-and-user-mode.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.