> 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/integrations/egnyte.md).

# Egnyte

Learn how to connect Couchdrop to Egnyte

## Overview

Couchdrop can connect directly to Egnyte and make your existing Egnyte storage available through Couchdrop.

Once connected, you can use files and folders in Egnyte with Couchdrop file transfer and workflow features without moving them into a separate storage platform.

## How to connect Egnyte

{% hint style="warning" %}

#### Before you start

To connect Egnyte, you will need:

* A licensed Egnyte account
* Your Egnyte domain
* Access to the Egnyte folders you want Couchdrop to use
  {% endhint %}

{% stepper %}
{% step %}

### Add a new storage connection

In Couchdrop, add a new storage connection and select **Egnyte** from the list of available connections.
{% endstep %}

{% step %}

### Configure Egnyte

Enter a **Name for this integration** and select the **Couchdrop folder path** where the connection will appear.

Enter your **Egnyte Domain** using your full Egnyte hostname, for example:

`yourdomain.egnyte.com`
{% endstep %}

{% step %}

### Authorize Couchdrop

Select **Authorize Egnyte**.

A window will open asking you to authorize Couchdrop to access Egnyte. Sign in if required, then select **Allow Access**.

Couchdrop uses the Egnyte APIs to list folder contents and upload, download, delete, and make changes to content stored in Egnyte. 

Select **Save and Test** to verify the connection with Egnyte.
{% endstep %}

{% step %}

### Select your folder

After the connection has been tested, you can optionally select a specific Egnyte folder to map into Couchdrop.

Leaving this blank allows Couchdrop to map the Egnyte connection without restricting it to a specific folder.

When a folder is selected, Couchdrop limits the connection to that location and its subfolders.
{% endstep %}

{% step %}

### Save and use your Egnyte connection

Optionally, configure **Transfer Shield** and select a content rule group to surface or block unexpected, non-compliant, or malicious files uploaded through this connection.

When the configuration is complete, save the integration.
{% endstep %}
{% endstepper %}

## Frequently asked questions

<details>

<summary>Does Couchdrop copy my Egnyte files into Couchdrop?</summary>

No. Couchdrop connects to your existing Egnyte storage and makes it available through Couchdrop. Your files remain stored in Egnyte.

</details>

<details>

<summary>Can I connect Couchdrop to a specific folder in Egnyte?</summary>

Yes. After the connection has been tested, you can optionally select a specific folder to map into Couchdrop.

If you select a folder, Couchdrop limits the connection to that location and its subfolders.

</details>

<details>

<summary>What happens if I do not select an Egnyte folder?</summary>

You can leave the folder selection blank. Couchdrop will map the Egnyte connection without restricting it to a specific folder.

</details>

<details>

<summary>How does Couchdrop access Egnyte?</summary>

Couchdrop connects to Egnyte through the Egnyte APIs after you authorize the integration.\
This allows Couchdrop to list folder contents and upload, download, delete, and make changes to content stored in Egnyte.

</details>

<details>

<summary>Can I use Egnyte with Couchdrop file transfer workflows?</summary>

Yes. Once Egnyte is connected, the mapped storage can be used with Couchdrop file transfer and workflow features.

</details>


---

# 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/integrations/egnyte.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.