Permission and Field Security Level not Considered when Creating a Candidate

Recruiting Center users have the ability to create candidates without the restriction of security level permissions and field security level.

When creating a candidate general profile or job-specific submission (via the Create Candidate action), the file presented to users will not take into consideration security level permissions in view and edit modes for those users and will allow them to input data into all the fields no matter the security level permissions granted or the security level set for the fields.

Security Level Permission Location
  • Security level for internal candidates (in edit mode)

  • Security level for internal candidates (in view mode)

  • Security level for external candidates (in edit mode)

  • Security level for external candidates (in view mode)

Configuration > [SmartOrg] Administration > User Types > Recruiting > Candidates

Security Level - Candidate Field Location
  • General

  • Restricted

  • Confidential

Configuration > [Recruiting] Administration > Fields > Candidate

Below is an example of a candidate creation process. In this example, the user does not have security level permissions in edit and view mode for the First Name and Last Name fields:

  • The user selects Create Candidate in the More Actions list.

  • When doing the duplicate check before creating the candidate, the user has access to the First Name and Last Name fields.

  • When creating the candidate, the user also has access to the First Name and Last Name fields.

  • Once fields have been filled, the user clicks Save or Save and Close. The system does a check to see if all mandatory fields are filled. If not, the user remains in the create candidate process until he/she fills in all mandatory fields and clicks Save or Save and Close again.

  • When all mandatory fields are filled, the user is then moved out of the create candidate process and into the edit or view candidate process. All security level permissions are then considered again. As a result, the user does not see the First Name and Last Name fields in view mode and in edit mode as he/she does not have the security level permissions for that.

Note that when creating a candidate job-specific submission, if the user does not have access (security level permissions) to view or edit the candidate file, the system will automatically redirect the user to the Recruiting Center home page. For example, if the user was creating an internal candidate and he/she is not allowed to see internal candidates, as soon as the user saves the file (that is, exit the create mode), the system will close the file and take the user back to the home page.