Skip to main content
BETA - Confidential Fields

Crelate allows for custom text fields to be Masked and/or Encrypted to control user visibility and access based on security privileges.

Natalia Salazar avatar
Written by Natalia Salazar
Updated over 3 weeks ago

Creating a custom field

To add a custom field to a record, navigate to the Settings area and choose Core Records. Choose the record type you would like to add a custom field to. When you select the record, options for the records of that type will appear in the middle of the screen. Choose the Customize Fields option:

A screenshot of a contact record

AI-generated content may be incorrect.

The prompt on the screen shows all of the fields currently on that record's form. Click the + sign in the top right of the prompt to begin creating a new custom field.

A screenshot of a custom field

AI-generated content may be incorrect.

Name your new field, and choose Text as the type of field.

Note: Only Text fields can be Encrypted or Masked.

If you click on Advanced, you will now see the ability to assign a Logical Name, and set Encryption and Masking.

  • Logical Name: Used when creating API Calls, and you can customize the Field Name to find it more easily in our code.

  • Encryption: The value in this field will be encrypted for added security. Because of this, Encrypted fields won’t appear in Search, Find, Client Portal, or external tools like the Chrome extension. Accessing it through the public API also requires special permissions. Setting a field as Encrypted does not inhibit users from accessing or editing a field value, instead, Encryption controls how the value stored in Crelate’s servers.

  • Off – The value is not encrypted (default)

  • On – The value is encrypted

  • Masking: The value in this field will be masked when viewed. Because of this, Masked fields won’t appear in Search, Find, Client Portal, or in external tools like the Chrome extension. Accessing it through the public API also requires special permissions.

  • Show All – No masking will be applied.

  • Show Last Four – The value will be masked with *****, only showing the last four characters. If the value is four characters or less, the entire value will be masked.

  • Show None – The entire value will be masked with *****.

Setting User Role Access to Masked Fields

Roles provide the ability for administrators to limit and control the experience of their users. The ability to create custom user roles in Crelate is a Business feature, however, Professional users can modify both the default roles to tailor the user experience for non-admin users.

To access and create roles in Crelate select: Settings | User Roles

From the desired Role type ability to Unmask fields from Crelate and view Unmasked Data and/or Encrypted Data over the API can be set.

  • View Unmasked Data – This toggle controls if the user can unmask data in masked fields and see/edit the values.

  • No – Users with this role cannot unmask masked fields.

  • Yes – Users with this role can unmask masked fields.

Note: Data entry into masked fields is possible without selecting Yes if setting a value for the first time.

  • View Unmasked Data via Public API

  • No – Users with this role cannot unmask masked fields via the Public API.

  • Yes – Users with this role can unmask masked fields via the Public API.

Note: Data entry into masked fields is possible without selecting Yes if setting a value for the first time.

  • View Decrypted Data via Public API

  • No – Users with this role cannot decrypt encrypted fields via the Public API.

  • Yes – Users with this role can decrypt encrypted fields via the Public API.

Note: If a Public API user does not have this privilege and requests encrypted fields, they will receive an error.


What's Next?

Did this answer your question?