The security based on Role-Based Permission (RPB) is defined in the MDF object definition. With the security, you can control which can view, edit, or import and export data in an object. With MDF, the security can be defined granularly and at the field level.
The job profile target role-based permissions, controlled with the following MDF Objects are:
- Job Profile
- Skill Profile*
- Rated Skills*
Note
*These MDF Objects (Skill Profile and Rated Skills) are relevant only to use the Skill Profile block which is only possible with JPB+CoC scenario. With Talent Intelligence Hub, skills are managed in the Growth Portfolio. This will be discussed in a later lesson.
From the Action search, navigate to Configure Object Definition.
Select Object Definition and choose Job Profile.
Scroll down to the Security section towards the end of the page and verify that you have the following options:
- Secured: Yes
- Permission Category: Manage Job & Skill Profile Visibility
- Leave the RBP Subject User Field field blank.
- CREATE Respects Target Criteria: No
Scroll to the bottom of the page and click Save to finish.
Repeat the same steps for the object definition Skill Profile and for Rated Skills. The only difference is that the RBP Subject User Field must be externalCode.
With these objects being secured, you can continue granting permissions:
- Navigate to Manage Permission Roles using Action search, and select the Administrator role. Choose the Edit option, under the Actions column. Navigate to the step 2. Add Permissions. The following permission must be granted:
- In the category General User Permission: User Login and Live Profile Access
- In the category Manage Job Profile Builder: Select All.
- In the category Metadata Framework: Select All.
- In the category Manage Job & Skill Profile Visibility: Select All.
- Choose Next and Save to save all changes. Log out and log back in to the instance.
Caution
The Field-Level Overrides option can be used to restrict permission for specific job profile fields, so that it isn't viewable or editable to individuals under specific permission roles. To avoid system issues, field level overrides must not be restricted for mandatory fields.