> 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/file-sharing/b2b-connect/receiving-files-with-b2b-connect.md).

# Receiving files with B2B Connect

Learn how to receive files using the B2B Connect feature

## Introduction

B2B Connect lets you give customers, suppliers, and other business partners a direct way to send files into a storage location you control.

You choose where received files are delivered, including connected storage such as SharePoint, Google Drive, or another supported storage location, then invite the sending organization to connect through their own Couchdrop account.

The sender does not need access to your storage platform or its credentials. Couchdrop handles the connection between both organizations, so files can move directly into your selected destination without being manually downloaded, emailed, or moved between systems.

{% hint style="info" %}
By default, neither party can browse or manage files in the other organization's storage.

You can optionally allow the paired connection to view files in the destination folder by editing the connection settings.
{% endhint %}

***

## Receive files with B2B Connect

Use this option when you want another organization to send files directly into a folder you control.

{% hint style="warning" %}

#### Before you start

To receive files with B2B Connect, you will need:

* Access to Couchdrop with the appropriate permissions
* The email address of the sending party
* A folder location where received files will be stored
  {% endhint %}

{% stepper %}
{% step %}

### Create the connection

In Couchdrop, select **B2B Connect** and create a new connection.

Choose to **initiate a connection**, then select **receive files**.
{% endstep %}

{% step %}

### Configure the inbound connection

Enter the email address of your business partner, name the connection, and choose the folder where received files will be stored.
{% endstep %}

{% step %}

### Send the invitation

Complete the configuration to send the invitation.

Your partner will be asked to name the connection in their own Couchdrop account and provide a name for the outbound B2B Connect folder that will appear in their file browser.
{% endstep %}
{% endstepper %}

## What the sending party does

The sending party does not need to connect a storage account to use the B2B Connect pairing.

They can send files directly from the **B2B Connect** page or upload files to the outbound B2B Connect folder created for the connection.

Files are delivered into the folder you selected when configuring the connection.

## Manual pairing

B2B Connect can also be paired without using the invitation email.

The initiating party can provide the pairing token directly to the other organization.

The other party can then create a B2B Connect connection, select **accept a pair request**, and enter the token to complete the pairing.

This is useful when the invitation needs to be shared through another communication channel or handled by a different person within the receiving organization.


---

# 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/file-sharing/b2b-connect/receiving-files-with-b2b-connect.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.