Configuring Permissions

Objectives

After completing this lesson, you will be able to:

  • Configure button permissions
  • Configure feature permissions

Button Permissions

Requisition buttons are given permissions dependent on the assigned roles.

The button permissions section includes the following elements:

  • <description>: The CDATA value is not displayed anywhere in the product

  • <role-name>: The CDATA value is used to store the valid roles; you may list multiple <role-name>elements within the <button-permission> block

  • <button-id>: The CDATA value is used to store the valid buttons. You may list multiple <button-id>elements within the <button-permission> block. The only valid buttons are closeReqand reopenReq:

    • closeReq: This allows the role to close the requisition.

    • reopenReq: This allows the role to reopen a closed requisition.

Button Permissions Zone

The button permissions zone allows you to assign permission to the Close Req and Reopen Req buttons.

You can assign permissions to buttons so that they are accessible by roles in zone 4 of the JRDM.

Feature Permissions

In the requisition, the following features of the recruiting system are enabled using feature permissions:

  • Interview Assessments

  • Offer Approvals

  • Offer Letters

  • Late-Stage Applications

  • Onboarding Letters

  • Application Historical Results

Enablement of Feature Permissions

Interview Assessment: This feature enables the Set up Interviewers link to add interviewers in the Interview portlet.

Offer Approval and Offer Letter: This feature enables the option to create an offer letter and initiate offer approval.

Late-Stage Applications: This feature enables the option to assign a candidate to a requisition, without first completing an application. The Invite Late Stage Applicant button only displays when the late stage application feature is configured for the requisition. This allows a user who has permission to add the candidate directly to the requisition, without the candidate submitting an application through the system. Unlike the Invite to Apply functionality available in the Forwarded status, the late stage application Invite to Apply can be selected multiple times. Both Invite to Apply features use the same email template. If late-stage application is used with multistage application, a candidate who responds to the invitation to apply sees all fields exposed in all statuses up to and including the status they are in.

Onboarding: This feature enables the option to select Create Onboarding Letter from the list of candidates in the Actions menu. This option does not appear in the list when the activity is disabled.

Application Historical Results: This feature enables the option for recruiting users, who have permission, to access the Historical Results tab on the job application page.

Additional Information on Feature Permissions

The following information is available:

  • Previous prescreening question and answer information for candidates forwarded from one job to another, where they have not yet applied.

  • Previous assessment scores and recommendations for applicants on jobs where the assessment was taken (available for customers using PeopleAnswers or SHL Assessment integration).

  • Previous background check and drug screening results for applicants (available for customers using VI and FADV integration).

Feature Permissions Zone

The following are features that are assigned permissions in the JRDM:

  • Interview Assessment

  • Offer Letter Creation

  • Offer Approval

  • Onboarding Letter Creation

  • Late Stage Application

  • Multi-Stage Application

Feature Permissions Section

  • You can assign permissions to features for one or more roles, and they can be available during one or more Candidate Applicant Statuses in Zone 10 of the JRDM.

  • In the figure, Feature Permissions Section, lateStageApp already existed for the Hired status.

Feature Permission Section in XML

To assign permissions to features, add the code from the figure, Feature Permissions Assignment, to your JRDM XML template (they apply to each activity block).

Note
When adding the code to your JRDM, everything is case and space sensitive.

Additional Feature Permissions

  • To have more than one status available for an activity, you add another of the code blocks for that activity with the additional status name.

  • The figure, Feature Permissions Section: Code, shows another block of code with the Offer Extended status.

Candidate Status Trigger

Each of the features described previously are ‘triggered’ by the candidate status.

You can enable the functionality automatically by simply moving the candidate to the desired status as follows:

  • Interview status enables the Interview functionality.

  • Offer status enables the Offer Approval and Offer Letter functionality.

  • Background Check status enables the option to add a candidate who has not previously applied to a requisition.

  • Onboarding status enables the option to use an Onboarding template to send an email with attachments.

  • Multi-Stage Application status enables the option to email the candidate, asking them to complete additional fields in the application (stage 2).

  • Application Historical Results status enables the recruiting user to view historical results on an application.

Hint
You can configure any feature to use any status or multiple statuses.

Use of Candidate Status to Enable Features

To enable features, you must add code to your Job Requisition Data Model XML template.

Everything is case and space sensitive.

They apply to each activity block.

  • In the <application status set> tag, insert the name of your status set.

  • The <role-name> tag defines which roles have permission to perform the activity.

  • In the <status> tag, insert the status name to which this permission applies, for example <![CDATA[Interview]]>.

Additional Candidate Statuses

To have more than one status available for an activity, add another block for that activity with the additional status name.

Application Historical Results Information

To enable features, add code to your JRDM XML template. Everything is case and space sensitive.

Application Historical Results Feature Permission

They apply to each activity block.

  • In the feature-permission tag, insert the name of the feature permission.

  • The <role-name> tag defines which roles have permission to perform the activity.

  • In the <status> tag, insert the status name to which this permission applies, for example <![CDATA[Interview]]>.

In addition to pre-screening questions, enabled users can also see historical results of background checks and assessment scores, if the customer has pre-configured integrations with VI, FADV, PeopleAnswers and SHL Assessment. More details are available in the implementation guide.

Interview Results

When the candidate is in the interview status or statuses, and the user has permission, you can see the Set up Interviewers link in the Interviews portlet. This link allows you to add interviewers.

In the figure, The Set Up Interviewers Link, you can see an example of this.

Offer Approval and Offer Letter Results

When the candidate is in the ’Offer’ status or statuses, and the user has permission, you can create an offer letter and initiate offer approval.

The figure, Offer Letter and Offer Approval, shows an example of this.

Onboarding Results

When the candidate is in the Hired status, and the user has permission, you can select Create Onboarding Email from the list of candidates in the Actions menu (the option does not display when this activity is disabled).

In the figure, Onboarding Email, you can see an example of this.

Late Stage Application Results

The late stage application feature enables the option to assign a candidate to a requisition, without first completing an application form.

The Invite Late Stage Applicant button displays when the late stage application feature is configured in the requisition. This allows a user, who has permission, to add the candidate directly to that requisition. In this scenario, the candidate is not required to submit an application through the system.

Application Historical Results

The Historical Results feature supports the ability to review historical results on the Job Requisition page.

The figure, Application Historical Results, show an example of this.

Log in to track your progress & complete quizzes