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

# Sending files with B2B Connect

Learn about how to send files with the B2B Connect feature

## Introduction

B2B Connect lets you send files directly to a business partner without needing access to their storage platform or credentials.

You create the outbound connection in Couchdrop and invite the receiving organization. They choose where the files will be delivered in their own Couchdrop account, including connected storage such as SharePoint, Google Drive, or other supported storage locations.

Couchdrop handles the pairing between both organizations, giving you a dedicated way to exchange files without creating shared storage accounts, guest users, or separate transfer credentials for each partner.

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

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

***

## Send files with B2B Connect

Use this option when you want to send files directly to another organization's Couchdrop-connected storage.

{% hint style="warning" %}

#### Before you start

To send files with B2B Connect, you will need:

* Access to Couchdrop with the appropriate permissions
* The email address of the receiving party
* A folder location to use for the outbound connection
  {% endhint %}

{% stepper %}
{% step %}

### Create the connection

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

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

{% step %}

### Configure the outbound connection

Name the connection, choose the outbound folder, and enter the email address of the receiving party.
{% endstep %}

{% step %}

### Send the invitation

Complete the configuration to send the B2B Connect invitation.

{% hint style="success" %}
After creating a new B2B connection, an outbound user icon will appear next to the connection in the B2B Connect list. This icon will disappear once the other party finishes their configuration, indicating that the connection is ready to use. 
{% endhint %}
{% endstep %}
{% endstepper %}

## What the receiving party does

The receiving party receives an invitation email with a link to complete their side of the connection.

They choose the directory where files sent through the connection will be delivered.

Their storage credentials remain in their own Couchdrop account and are not shared with you.

Once they complete the configuration, the B2B Connect pairing is ready to use.

## 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/sending-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.