> 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/storage/file-browser.md).

# File Browser

Learn about how to use Couchdrop's file browser

## Overview

Couchdrop's File Browser gives you a single place to browse files and folders across your connected storage platforms.

Folders in the File Browser map to your storage connections, allowing you to view, upload, and download files without accessing each storage platform separately.

{% hint style="info" %}
Folders in the File Browser map directly to your storage integrations. For more information about how storage is presented in Couchdrop, see [Virtual Folders](/how-couchdrop-works.md). 
{% endhint %}

## Using the File Browser

When you [set up a storage connection](/storage/overview.md), you select the folder or storage location that Couchdrop will use as the root of that connection.

This location becomes the highest-level folder available through Couchdrop. Any parent folders above the configured root are not surfaced in the File Browser.

Because each storage connection appears as a folder, you can connect storage from multiple platforms and browse them through the same interface.

Users with access to the Couchdrop web portal can also interact with files stored in these connected locations, subject to their configured permissions.

{% hint style="info" %}
Folders used by configured file transfer features, such as Mailboxes or Shared Links, display an **In Use** icon beside the folder.
{% endhint %}

Couchdrop's File Browser is focused on file transfer and access rather than document collaboration. It does not provide live document editing or the collaboration features available in platforms such as Google Drive or Dropbox.

Instead, the File Browser gives you centralized visibility across connected storage while allowing access, security, and transfer controls to be applied at the folder level.

## Managing settings and permissions

You can configure permissions and security controls for individual folders in Couchdrop's virtual file system.

<table><thead><tr><th width="191.2734375">Setting</th><th>Description</th></tr></thead><tbody><tr><td><strong>Permissions</strong></td><td>Control user and group access to the folder using read and write permissions.</td></tr><tr><td><strong>Notifications</strong></td><td>Send an email or webhook notification when an upload, download, or transfer failure involves the folder.</td></tr><tr><td><strong>Encryption</strong></td><td>Automatically PGP encrypt files when they are uploaded and/or PGP decrypt files when they are downloaded from the folder.</td></tr><tr><td><strong>Approval</strong></td><td>Require approval for file uploads or for creating Shared Links that point to the folder.</td></tr><tr><td><strong>Transfer Shield</strong></td><td>Apply content classification and rules using <a href="/security-and-governance/transfer-shield-dlp.md">Transfer Shield</a>. </td></tr></tbody></table>

Folders with modified settings display an icon beside the folder name indicating that custom permissions, security, or other folder-level settings have been applied.


---

# 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/storage/file-browser.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.