> 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/permissions/features-access.md).

# Features Access

Learn about feature access rights on users and groups

## Overview

Feature Access controls which Couchdrop services and features a user can use.

These controls are separate from standard user roles. You can use them to allow or restrict access to individual connection methods and Couchdrop features on a per-user or [group](/administration/user-and-group-management/groups.md) basis.

When a user is created, Couchdrop applies reasonable defaults based on your environment. You can change these settings afterward as required.

## Configure Feature Access for a User

To manage Feature Access for an existing user:

1. Open the **Admin Panel**.
2. Select **All Users**.
3. Edit the user you want to configure.
4. Open **Access Controls**.
5. Select **Advanced**.
6. Configure the required options under **Features and Services**.

### Features and Services

The following controls are available.

<table data-search="false"><thead><tr><th width="290.0703125">Setting</th><th>Description</th></tr></thead><tbody><tr><td><strong>Allow SFTP and SCP Connections</strong></td><td>Allows the user to connect using SFTP and SCP on port 22.</td></tr><tr><td><strong>Allow FTP/FTPs</strong></td><td>Allows the user to connect using FTP and FTPs.</td></tr><tr><td><strong>Allow Upload Portal</strong></td><td>Allows the user to access the Inbox upload portal.</td></tr><tr><td><strong>Allow Web Portal</strong></td><td>Allows the user to access the main Couchdrop web interface at <code>my.couchdrop.io</code>.</td></tr><tr><td><strong>Enable Shared Links</strong></td><td>Allows the user to create and manage Shared Links. Non-admin users can only manage links they created.</td></tr><tr><td><strong>Enable Inboxes</strong></td><td>Allows the user to create and manage external Inboxes. Non-admin users can only manage Inboxes they created.</td></tr><tr><td><strong>Enable Automations and Actions</strong></td><td>Allows the user to create and manage Automations. Non-admin users can only manage Automations they created.</td></tr><tr><td><strong>Enable Inbound AS2 Stations</strong></td><td>Allows the user to create and manage AS2 Stations. Non-admin users can only manage AS2 Stations they created.</td></tr></tbody></table>

## How Feature Access works with roles

[User roles](/administration/user-and-group-management/user-roles.md) determine the user's broader level of access within Couchdrop.

Feature Access provides an additional layer of control by determining which services and features that user can use.

For example, you can give a user access to the **Web Portal** without allowing **SFTP and SCP Connections**, or allow them to create **Shared Links** without enabling **Transfer Automations and Actions**.

For more information on broader permission controls, see [Permissions](https://docs.couchdrop.io/~/changes/210/administration/permissions).


---

# 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/permissions/features-access.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.