> 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/get-started/set-up-an-sftp-user-and-endpoint.md).

# Set up an SFTP user & endpoint

Set up an SFTP endpoint and receive your first file using Couchdrop-hosted storage.

## Introduction

When you create a Couchdrop trial, Couchdrop-hosted storage is automatically set up in the region selected during signup.

In this guide, you will create an SFTP user, connect to your Couchdrop SFTP endpoint, and upload your first file.

{% hint style="warning" %}

#### Before you start

The admin user created during signup is the account owner.

Account owners do not have file transfer access enabled by default. We recommend leaving this unchanged and creating a separate user for SFTP access.
{% endhint %}

{% stepper %}
{% step %}

### Create an SFTP user

In Couchdrop, select:

**+ Create → Create SFTP or FTP User**

Select **SFTP User**.
{% endstep %}

{% step %}

### Configure the user

For **Username**, use the autogenerated username or enter your own.

For **Root directory**, select the root directory in the folder picker.

For **Password**, select **Autogenerated Password**.

Leave **Public and Automatic RSA Key creation** disabled for this guide.

{% hint style="info" %}
A root directory limits the user to a specific folder in Couchdrop or connected storage. The user cannot browse outside that location or identify the underlying storage.
{% endhint %}

Click **Create user**.
{% endstep %}

{% step %}

### Save your credentials

Couchdrop displays the new user's:

* Username
* Password
* SFTP endpoint
* Private key, if enabled

Your SFTP endpoint will look similar to:

`sftp://username@your-subdomain.couchdrop.io`

{% hint style="warning" %}
Copy or download the credentials before leaving this page.

Generated passwords and private keys are not stored by Couchdrop and cannot be displayed again.
{% endhint %}
{% endstep %}

{% step %}

### Connect and upload a file

Open your SFTP client and connect using:

| Setting      | Value                         |
| ------------ | ----------------------------- |
| **Host**     | `your-subdomain.couchdrop.io` |
| **Port**     | `22`                          |
| **Username** | Your new username             |
| **Password** | Your generated password       |

Upload a small test file.
{% endstep %}

{% step %}

### Check the file arrived

Open **File Browser** in Couchdrop.

Your test file should appear in the root directory.

You can also open **Activity** to confirm the upload.
{% endstep %}
{% endstepper %}

## Next steps

You now have a working SFTP endpoint and have received your first file through Couchdrop.

Next, **connect your existing storage** so files can be delivered directly to the platform where they need to live.


---

# 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/get-started/set-up-an-sftp-user-and-endpoint.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.
