# Configuration

## Keys

A "Key" concept of the automation utility is that we don't store sensitive information (like connection strings, SFTP information, etc) inside the package. Instead, we reference the keys they belong to.

Let's say we're transforming data from <mark style="color:orange;">**Pizzeria**</mark>'s SFTP server to a local <mark style="color:orange;">**Reporting**</mark> folder. We would configure our source to be an SFTP server with the <mark style="color:orange;">**Pizzeria**</mark> key, and the target to be a folder with the <mark style="color:orange;">**Reporting**</mark> key.&#x20;

<figure><img src="/files/V4c3P59rE9LeCVh2ObHi" alt=""><figcaption><p>Keys</p></figcaption></figure>

To actually provide the secure SFTP credentials, and the folder path, you would do so locally alongside your client application.&#x20;

<figure><img src="/files/fNKj5Cqr3QvwFJewENzh" alt=""><figcaption><p>Client config</p></figcaption></figure>

## Encryption / Decryption

The application supports both encryption and decryption of the settings.json file associated with the application.&#x20;

### Encrypt

To encrypt, run the application with the **`-e`** flag followed by the password. An example:

```
TransformClient.exe -e "Expelliarmus"
```

The application credentials will now be encrypted and not visible under inspection.&#x20;

{% hint style="success" %}
The application will create a **.bak.json** file of the credentials before attempting to encrypt. This is to prevent data loss or accidents. <mark style="color:red;">**If you're satisfied with the encrypted results, don't forget to delete this file**</mark>.&#x20;
{% endhint %}

<figure><img src="/files/zwNgOXOXrnPglKbhoRKb" alt=""><figcaption></figcaption></figure>

### Decrypt

To decrypt, send the **`-d`** flag. An example:

```
TransformClient.exe -d "Expelliarmus"
```

And just like that, if the passwords matched, you'll get a decrypted result.&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.perigee.software/transforms/automation/configuration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.