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

# Folder Permissions

Learn about configuring folder permissions in Couchdrop

## Overview

Folder Permissions let you control what users and groups can do within specific folders in Couchdrop.

Permissions apply regardless of how the user accesses Couchdrop, so the same controls apply across supported connection methods and the Web Portal.

## How Folder Permissions work

Couchdrop uses an inheritance model for folder permissions.

By default, a folder inherits permissions from its closest parent folder. When you configure permissions directly on a folder, that folder stops inheriting permissions from its parent.

{% hint style="warning" %}

### Important

When enabling permissions on a folder you must keep in mind:

* By default, access to the folder will be denied to all users
* Enabling permissions on a folder breaks the inherited permissions

To grant access you must:

* Select a user or group for the permission
* Add user permissions.
  {% endhint %}

To configure access to a folder:

1. Open the folder in Couchdrop.
2. Configure permissions for that folder.
3. Select the **User** or **Group** that should receive access.
4. Enable the permissions they require.

### Available permissions

Folder Permissions are granular, allowing you to control individual actions.

<table data-search="false"><thead><tr><th width="214.2265625">Permission</th><th>Description</th></tr></thead><tbody><tr><td><strong>List Contents</strong></td><td>Allows the user to list files and folders inside the folder.</td></tr><tr><td><strong>Get Properties</strong></td><td>Allows the user to retrieve properties for files and folders.</td></tr><tr><td><strong>Delete</strong></td><td>Allows the user to delete files and folders.</td></tr><tr><td><strong>Upload</strong></td><td>Allows the user to upload files into the folder.</td></tr><tr><td><strong>Download</strong></td><td>Allows the user to download and read files.</td></tr><tr><td><strong>Share</strong></td><td>Allows the user to create Shared Links for files and folders.</td></tr><tr><td><strong>Create Inbox</strong></td><td>Allows the user to create an Inbox for the folder and its children.</td></tr><tr><td><strong>Manage Permissions</strong></td><td>Allows the user to manage permissions on the folder.</td></tr><tr><td><strong>Manage Notifications</strong></td><td>Allows the user to manage notifications for the folder.</td></tr></tbody></table>

Folder Permissions can be combined with a user's [home/root directory](/administration/user-and-group-management/root-directory.md) to provide more granular access within the portion of the filesystem available to that user.

### Permission inheritance

Permissions are inherited from the closest parent folder unless you configure permissions directly on a child folder.

For example, if permissions are configured on:

`/Customers`

folders beneath it inherit those permissions:

`/Customers/Acme`

`/Customers/Contoso`

If you then configure permissions directly on:

`/Customers/Acme`

that folder uses its own permission configuration instead of inheriting the permissions from `/Customers`.

This lets you define broad access at a parent folder and override it where individual folders require different controls.

## Folder Sharing

Folder Sharing uses the same permission model as Folder Permissions, but additionally makes the folder visible from the user's home directory.

To share a folder this way, enable **Appear in users home directory** when configuring its permissions.

The shared folder will then appear as a link from the user's root directory, allowing them to access a folder that would not otherwise appear there.

This is useful when a user needs access to specific folders without changing their configured [home/root directory](/administration/user-and-group-management/root-directory.md).


---

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