Manual GPG Encryption and Decryption
Files.com can GPG encrypt or decrypt a single file as a one-time action you start in the File Manager or GPG Key Manager. Neither an Automation nor a GPG folder setting is required. Use it to encrypt a file before sending it to a partner who requires GPG, or to decrypt a file a partner sent you.
For unattended work, use an explicit GPG step in Automations v2 or GPG Folder Processing for incoming files at a receiving location. Choosing how GPG runs explains those options and how Automations v1 relies on folder settings.
The keys available for manual encryption and decryption depend on your administrative access and key ownership within the current Workspace. When you switch Workspaces, the available keys change to match.
| Administrative Access | Available GPG Keys |
|---|---|
| Site Administrator | Any key in the current Workspace, including keys owned by users or Partners. |
| Workspace Administrator | Any key in a Workspace they administer, including keys owned by users or Partners. |
| Folder Administrator | Keys owned by their own user account, such as keys they create or import for themselves. |
| Partner Administrator with Allow Providing GPG Keys enabled | Keys owned by their own user account and keys owned by their Partner. Keys owned by another individual Partner User are not included. |
Folder administration and GPG key access are separate permissions. Files.com can process incoming files under a GPG folder setting with a key supplied by a Site Administrator without making that key available to Folder Administrators for manual operations. If you have no accessible GPG keys, the File Manager does not show GPG Encrypt or GPG Decrypt.
Through the API, these actions require a Full Access API key with the required file and GPG key permissions. A Files Only API key cannot run GPG Encrypt or GPG Decrypt, regardless of its associated user's administrative permissions or whether it is a site-wide key. GPG encryption and decryption configured as folder settings still apply to files uploaded with a Files Only key.
File Size
Manual GPG encryption and decryption work on files up to 10 GB. The GPG file-size limit reflects the CPU capacity needed to process each file. Contact Files.com Support if your workflow requires larger files.
Encrypting a File
When you encrypt a file, you decide who will be able to open it by choosing whose key to encrypt with. To send the file to a partner, encrypt it to that partner so that only they can decrypt it.
To keep it for yourself or for a counterparty whose key you store on your site, encrypt it to one or more keys from the GPG Key Manager. A single file is encrypted either to stored keys or to one partner, not to both.
The encrypted file is binary by default, which is the recommended choice for most transfers. If you are sending it over a channel that only accepts plain text, such as email, choose ASCII-armored output instead.
You can also sign the file with one of your private keys. A signature lets the recipient confirm the file came from you and was not altered along the way.
Decrypting a File
When you decrypt a file, Files.com tries the private keys you can access and uses the one that opens the file, so you usually do not need to know which key it was encrypted to. If you would rather control it, you can choose the keys yourself: specific keys from the GPG Key Manager, or a key from a partner.
If a file will not decrypt because of a modification detection code error, you can retry with Ignore MDC integrity check enabled. Only do this when you trust where the file came from and know the error is a compatibility quirk, not a sign that the file was tampered with.
Choosing the File and Where the Result Goes
In the File Manager, select a file whose name does not end in .gpg or .pgp and choose GPG Encrypt. For a file whose name ends in .gpg or .pgp, choose GPG Decrypt. These extensions are recognized regardless of capitalization.
You can also start from the GPG Key Manager by choosing Encrypt File or Decrypt File on a key, which begins the action with that key already chosen.
Output File Names
When you encrypt a file, the suggested output name is the original name with .gpg appended. For example, encrypting report.csv suggests report.csv.gpg. When you decrypt a file, the suggested output name is the original name with the final .gpg or .pgp removed, regardless of capitalization. For example, decrypting report.csv.PGP suggests report.csv.
The result is saved as a new file. By default it goes in the same folder as the original, but you can choose a different folder and edit the suggested output name before starting the operation. If a file with the same name already exists at the destination, the operation fails unless you select Overwrite existing file and have permission to replace that file.
The destination folder's settings still apply to the new file. Choose a destination without an additional GPG folder rule unless that further processing is intended.