> 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/administration/encryption-keys.md).

# Encryption Keys

## Overview

Couchdrop uses encryption keys and certificates across features including SFTP authentication, PGP encryption, and AS2.

The **Administration > Keys** page provides a central location where administrators can add and manage keys configured for the Couchdrop account. This includes SSH private and public keys, PGP private and public keys, and AS2 keys and certificates.

Centralizing these credentials allows keys to be configured once and reused by administrators where supported across Couchdrop.

{% hint style="info" %}
All encryption keys must be in PEM format to work across Couchdrop. If your key uses a different format, follow our guide on converting keys to a compatible PEM format before adding it.
{% endhint %}

## Managing encryption keys in Couchdrop

{% hint style="warning" %}

#### Before you start

To manage encryption keys, you will need:

* Access to Couchdrop with the appropriate administrative permissions.
* The key or certificate you want to add.
* Keys in a format supported by the feature where they will be used.
  {% endhint %}

{% stepper %}
{% step %}

### Open Encryption Keys

In Couchdrop, navigate to **Administration > Encryption Keys**.

This page lists the encryption keys currently configured on your account.
{% endstep %}

{% step %}

### Add an encryption key

Click **Add Key** to configure a new key.

Provide the required key information and save the key to make it available for supported Couchdrop features.

{% hint style="success" %}
Once your encryption keys have been added, they can be selected by supported Couchdrop features without maintaining separate copies of the same key for each configuration.
{% endhint %}
{% endstep %}

{% step %}

### Review configured keys

Use the **Encryption Keys** table to review existing keys and identify who created or last modified them.

The **Encryption Keys** table provides the following information:

<table data-search="false"><thead><tr><th width="183.53125">Field</th><th>Description</th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>The name assigned to the key.</td></tr><tr><td><strong>Encryption</strong></td><td>The encryption or key format, such as <code>PEM</code> or <code>PGP</code>.</td></tr><tr><td><strong>Type</strong></td><td>Identifies whether the configured key is <strong>Private</strong> or <strong>Public</strong>.</td></tr><tr><td><strong>Created by</strong></td><td>The Couchdrop administrator who created the key.</td></tr><tr><td><strong>Last modified by</strong></td><td>The administrator who most recently modified the key.</td></tr><tr><td><strong>Created date</strong></td><td>When the key was originally added.</td></tr><tr><td><strong>Last modified</strong></td><td>When the key was most recently changed.</td></tr></tbody></table>
{% endstep %}
{% endstepper %}

## Using encryption keys in Couchdrop

### Using SSH keys

SSH keys can be used for key-based SFTP authentication. Couchdrop supports public key authentication for SFTP users and private keys when connecting to external SFTP servers.

For more information, see [using SFTP SSH keys](/walkthroughs/using-sftp-ssh-keys.md).

### Using PGP keys

PGP private and public keys can be managed from **Encryption Keys** for use with Couchdrop features that require PGP encryption or decryption.

### Using AS2 keys and certificates

AS2 keys and certificates can also be managed from **Encryption Keys** for use with Couchdrop AS2 configurations.

For additional configuration guidance, see the [Couchdrop AS2 documentation](/managed-file-transfer/as2.md).


---

# 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/administration/encryption-keys.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.