Question

Users X and Y need to see the same candidate record. For security reasons, user Y should NOT be able to view and report on the Email Address field on the record. How would a developer meet this requirement?

1) Use a custom Visualforce page to make the email address visible to user X but not user Y
2) Use field-level security to make the email address visible to user X but not user Y
3) Use a sharing rule to make the email address only visible to user X
4) Use page layouts to make address visible to user X but not user Y

Answer 1

To meet the requirement, a developer can use field-level security to control access to the Email Address field based on user profiles.

Step-by-step explanation:

The developer can meet this requirement by using field-level security. Field-level security allows the developer to control access to specific fields on an object based on user profiles and permissions. In this case, User X can be given access to view and report on the Email Address field, while User Y's profile can be configured to prohibit access to that field.

Using a custom Visualforce page, sharing rule, or page layouts will not meet the requirement as effectively as field-level security. A custom Visualforce page would require additional development effort and may not provide the same level of security. Sharing rules and page layouts can control access to records, but not specific fields within those records.