| Editions Available: All Editions | Audience: |
About Encrypted Fields
Overview
This article outlines frequently asked questions about encrypted fields.
Frequently Asked Questions
What is an encrypted field?
An encrypted field is used to store sensitive information that is encrypted at the database level but can be viewed within Bullhorn.
Only EEOC fields and fields with the field type customencryptedtext can be encrypted. You cannot encrypt other field types.
Are encrypted fields visible to all of my users?
Encrypted fields are visible to all users. You may identify them as confidential fields if you want to restrict visibility. To see how to make a field confidential, see Understanding Confidential Fields.
Can I access encrypted fields using APIs?
You may access encrypted fields using REST API but not SOAP. When accessing the encrypted fields via APIs the information will be decrypted.
Which entities support encrypted fields?
Candidate, Placement, and Placement Change Requests.
How can I view encrypted fields?
Encrypted fields can be added to records but cannot be added to list views and are not searchable.
How can I identify encrypted fields?
On the Candidate and Placement entities, all custom encrypted fields display a lock indicator beside the field name value.
These EEOC fields are encrypted but will not show a lock indicator:
- Social Security Number
- Veteran Status
- Ethnicity
- Disability
Can I pull information from an encrypted field into Canvas?
Encrypted field information can't be viewed within Canvas.
Does DataMirror include encrypted fields?
Yes, encrypted fields can be reported against in Data Mirror 8.