Skip to end of metadata
Go to start of metadata


Granting Access to Career Worksheet Tab

Grant the required role-based permission so that the permitted roles can access Career Worksheet tab under Development.

  1. Go to Admin Center Manage Permission Roles.
  2. Choose the role or roles to assign access and click Permission.
  3. Go to the User Permissions section and select Career Development Planning.
  4. Make sure that Career Development Plan (CDP) Access Permission is enabled. This checkbox controls the access to Development.
  5. Enable Career Worksheet Access Permission. You can also enable Career Worksheet Suggested Roles Access Permission, which allows the role to access the Career Worksheet Suggested Roles tab.


Granting Access Permission to the Career Worksheet Template

The permission to template is managed by target population. For example, an employee can view his or her own career worksheet plan but isn’t allowed to view others’ plans. A manager, however, can view the career worksheet plans of his or her direct reports.

  1. Go to Admin Center Manage Permission Roles.
  2. Choose the role or roles to assign access and click Permission.
  3. Go to the User Permissions section and select Objectives.
  4. Enable Objective Plan Permissions, and make sure that the relevant career worksheet template is selected by either by granting permissions to all templates or granting permission to individual templates.
  5. Click Done to save the settings.
  6. Go to Grant this role to… section and define a target population for the role permission.
  7. Save your changes.


Permission Settings in Career Worksheet Template

The detailed permission to target job roles and read permission to certain fields in a career worksheet plan are defined in the career worksheet template. Note that the career worksheet template can only be exported for editing through Provisioning.


Permission Roles

The permissions in the career worksheet template are assigned based on roles, and the common roles that you can use are as follows:

  • E: Employee

  • EM: Employee’s managers, including all the managers in the reporting line

  • EH: Employee’s HR manager

  • EX: Employee’s matrix manager

  • *: All users in the system

Permissions over Target Job Roles

You can define detailed permissions over the target job roles in the Roles I’m Considering... section, that is, who can view, add, or remove target job roles of an user.

Following are the available permissions and XML definition examples that you can use in the template file:



Permission

Description

XML Definition Example

private-access

The permission to view the available target roles of an employee.

Employees themselves, all the managers in their reporting lines, and their HR manager can view the target roles. For this scenario, you can define the definition as follows:

<permission for="private-access">    
<description><![CDATA[Employees and their managers up the reporting chain may view “Job Roles I’m Considering”.]]></description> <role-name><![CDATA[E]]></role-name> <role-name><![CDATA[EM+]]></role-name> <role-name><![CDATA[EH]]></role-name> </permission>

create

The permission to add target job roles for the employee.

Only the employees themselves and their direct managers can add target job roles. For this scenario, you can define the definition as follows:
<permission for="create">
    <description><![CDATA[Only the employee and their direct manager may add a role in a user's worksheet.]]></description>
    <role-name><![CDATA[E]]></role-name>
    <role-name><![CDATA[EM]]></role-name>
</permission>

delete

The permission to remove target job roles from the section.

Only the employees themselves can remove target job roles. For this scenario, you can define the definition as follows:

<permission for="delete">
    <description><![CDATA[Only the employee may delete role in his/her worksheet.]]></description>
    <role-name><![CDATA[E]]></role-name>
</permission>


Fields for Read Permission

You can define the read permissions for the fields in the career worksheet plans. Note that the write permission is not supported.

The read permission can be defined for the following fields:

field-definition idDescription
readiness_meter
The percentage rate of readiness for the target roles.
development_goals

Development goals associated with each competency or behavior. The number of development goals and the button to add a new development goal are displayed by default. But the details of the development goals nested under a competency or behavior is controlled by the permission defined here.

By default, the read and write permissions for the user are derived from the development plan template configuration. If a user doesn’t have permission to view the development goals, even he or she is granted the read permission in the career worksheet template, he or she still cannot view the details of the goals.

competency_name

Name of Competencies field. If a role has the read permission to other competency-related details (for example, last_rated_date and last_rated_form), this read permission to competency_name should also be granted. Otherwise, the competency will be listed as “undefined” as its name.

last_rated_date
last_rated_form
The date on which the competency was last rated and the form in which the competency was last rated. A graphical representation of comparison between the expected competency rating and the user’s latest rating.
last_rating

The user’s latest competency rating. Note that the read permission for last_rating is prerequisite for a user to view the graphical representation (gap_graph). If you have defined the read permission for gap_graph, define it for last_rating as well.




  • No labels