Encrypting Data

Archer allows you to encrypt the following field types in an application: Attachment, Date, IP Address, Image, Numeric, and Text.

The purpose of encryption is to protect sensitive data in the database and the file repository. With field-level encryption, you can use your own encryption keys to secure data. These keys are managed exclusively by you, ensuring Archer cannot access the encrypted content. Encrypted field data is stored in the Encrypted folder in the file repository. When you encrypt a field, all data in that field, whether in the record or through a data feed or import, is encrypted in the database. Encrypted fields display data in the record as normal text. Files and images associated with encrypted attachment and image fields are decrypted when downloaded. You can encrypt new and existing fields.

Encrypt a field

When adding or editing field options, select Encrypt Field Data to encrypt the field.

Note: You can disable encryption for an existing encrypted field by clearing the checkbox.

Complete the following tasks:

• Adding Date Fields
• Adding IP Address Fields
• Adding Numeric Fields
• Adding Text Fields
• Adding Attachment Fields
• Adding Image Fields

Note: Encrypted attachments and images are located in the Encrypted folder in the file repository.

Impact of Encrypted Fields in Archer

Encrypted fields enhance data security by protecting sensitive information. However, due to encryption constraints, certain operations like search and filters access have limited support.

The following table shows how encrypted fields affect other functionality in the application or Archer.

Related Area	Impact
Calculations	You cannot reference encrypted fields in a calculated field. You can calculate encrypted fields.
Data feeds/imports	If the incoming data targets an encrypted field, the data will be stored in the database in an encrypted format. Archer to Archer data feeds support encrypted attachments and images. When encrypted files are exported from an instance, they are unencrypted. If the target instance has encryption enabled, the files are encrypted. If the target instance does not have encryption enabled, the files are not encrypted.
History log	History logs are kept for encrypted fields.
Search (global search)	Encrypted fields are not supported.
Advanced search filters	Encrypted fields support only Equals and Does Not Equal filters. Encrypted fields cannot perform statistical search operations, for example Group By and Count.
Layout rule filters	Encrypted fields are supported for all standard field filter options in a layout rule.
Record Lookup Configuration	Only the filter options Equals, Does Not Equal, Field Value Match, and Field Value Does Not Match are available for encrypted fields.
Subscription Notification filters	Only the filter options Equals, Does Not Equal, Field Value Match, and Field Value Does Not Match are available for encrypted fields.