> For the complete documentation index, see [llms.txt](https://docs.reachplatform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reachplatform.com/customizations-and-bolt-ons/bolt-ons-catalog/custom-sftp-setup.md).

# Custom SFTP Setup

Deliver standard Reach reports to your systems through a secure SFTP drop.

### Overview

This bolt-on delivers **standard Reach reports** to an **SFTP folder** owned by your brand.

* **What it is:** A secure SFTP “drop” for scheduled report files.
* **Why teams use it:** Feed reports into BI, reconciliation, or downstream systems.
* **Who it is for:** Operations, finance, analytics, and your IT/security team.

{% hint style="info" %}
SFTP access uses **SSH keys** plus **IP allowlisting**. Password logins are not supported.
{% endhint %}

<a href="https://datami.atlassian.net/helpcenter/Boltons/portal/1488/group/1848/create/2353" class="button primary" data-icon="cart-shopping">Buy this bolt-on</a>

### Typical use cases

* Pull **nightly** or **weekly** report files into your data stack
* Reconcile **usage** and **billing** with internal systems
* Provide controlled access to a **trusted external partner**

### How access works

* Each brand gets an **isolated folder**
* Parent brands can receive **aggregated files**
* Many reports can also be viewed in **Reach Central**

### Scope

* **What is included:**
  * **Brand-specific SFTP user** and folder setup
  * Delivery of supported **standard reports** on an agreed cadence
  * **SSH key authentication** and **IP allowlisting**
  * Optional **GPG encryption**
* **What is excluded:**
  * **Real-time** or **streaming delivery**
  * **Password-based authentication**
  * **Custom report development**

### Brand inputs

Send the following to Reach:

* **Egress IP address(es)** to allowlist (public IP your SFTP client connects from).
* **SSH public key** (for key-based login).
* **GPG public key** (optional, if you want encrypted `.gpg` files).
* Whether you need **parent-level aggregated reporting** (if applicable).

### Setup flow

{% stepper %}
{% step %}

#### Prepare access details

Collect allowlist IPs and your SSH public key.

If you want encryption, also prepare a GPG public key.
{% endstep %}

{% step %}

#### Email the setup package

Send everything to `accounts@reachmobile.com`.
{% endstep %}

{% step %}

#### Reach provisions access

Reach creates the SFTP user and configures folder permissions.
{% endstep %}

{% step %}

#### Validate and confirm delivery

Reach shares the endpoint, username, and folder path.

You confirm you can connect and download files.
{% endstep %}
{% endstepper %}

### Troubleshooting

* **Connection refused**
  * Your connecting IP likely isn’t allowlisted.
  * If your IP changed, email the new IP to `accounts@reachmobile.com`.
* **Authentication failed**
  * Your private key doesn’t match the registered public key.
  * Confirm you’re using the same keypair you shared during setup.
* **Encrypted files won’t decrypt**
  * Confirm the correct GPG private key and passphrase are available.
* **Aggregated parent report is missing a child brand**
  * Confirm parent/child brand mapping is current.

{% hint style="info" %}
Setup, access, and delivery issues: `accounts@reachmobile.com`
{% endhint %}

### Requesting this bolt-on

For the standard request process, commercial notes, and support, see [Bolt-ons catalog](/customizations-and-bolt-ons/bolt-ons-catalog.md).

### Technical details

For the implementation-specific setup details, visit: [Brand SFTP set-up technical details](https://reachplatform.gitbook.io/reachplatform-docs/technical/~/revisions/b3C3M4tkkLMyqmMcGAsL/bolt-on-setup/custom-sftp-setup)

### Frequently asked questions

#### Can we use password authentication?

No. SFTP access requires an SSH key and IP allowlisting.

#### What happens after we purchase?

Reach collects your connection and encryption details.

<a href="https://datami.atlassian.net/helpcenter/Boltons/portal/1488/group/1848/create/2353" class="button primary" data-icon="cart-shopping">Buy this bolt-on</a>

{% hint style="info" %}
Questions or clarification? Reach out to your respective account manager or email us at <account-desk@reachplatform.com> for help and support.
{% endhint %}


---

# 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.reachplatform.com/customizations-and-bolt-ons/bolt-ons-catalog/custom-sftp-setup.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.