Steps: Set Up Security for Change Job
This topic is relevant to the enhanced change job experience. The new change job experience is available to all customers at this time.
Security:
Business Process Administration
or Manage: Business Process Definitions
, and Security Configuration
domains in the System functional area.Set up security to give managers and administrators access to the
Change Job
business process and subprocesses. The business process security policy specifies who can start or complete actions in the Change Job
business process.- ProvideViewandModifyaccess to theStaffing Actions: Change Job Date and Reasondomain. Users withViewandModifyaccess to this domain can edit all fields on the Job Change section in a Change Job event.
- Access theView Business Process Templatereport.
- Access theEdit Business Process Security Policytask.
- Select theChange Jobbusiness process type.
- Edit the business process security policy:
- UnderWho Can Start the Business Process, select the security groups you want to grant access to for each initiating action.Since theChange Jobbusiness process has multiple initiating actions, you can limit the types of job changes available to different roles. Example: You can restrict access to theChange Contingent Worker Detailstask, but provide broader access to theChange LocationandRequest Transfertasks.To hide tasks that aren't relevant, leave the security groups empty.You can only secure theRequest Transferinitiating action to constrained role-based security groups because it’s only available to roles that don’t have access to theChange Jobtask for the selected worker.
- UnderWho Can Do Action Steps in the Business Process, select the security groups you want to be able to complete review steps in the business process.
- UnderWho Can Do Actions on Entire Business Process, grant permissions to theHR Partner,HR Administrator, or other relevant HR role in your organization.To ensure that business process validations run, you must also grantView Allpermission to the roles that can initiate the business process.
- UnderAttachment Settings in BP Toolbar, define attachment security to restrict who can add, edit, and view attachments in business process events.
- (Optional) If you consolidateChange JobwithAssign Employee Collective Agreement,Change Organization Assignments for Worker, andPropose Compensation Change, set up security for these processes.If you're consolidating Change Job with:
- Assign Employee Collective Agreement, also grant security permissions to theWorker Data: Collective Agreementsdomain.
- Change Organization Assignments for Worker, also grant security permissions to theStaffing Organizations: Headerdomain.
- Propose Compensation, also grant security permissions to these domains:
- Add CompensationandCompensation Changein the Core Compensation functional area.
- Add Compensation Management PlansandChange Compensation Management Plansin the Advanced Compensation functional area.
- (Optional) Access theConfigure Optional Fieldtask to configure fields as hidden, view-only, or required.TheChange Jobbusiness process is available for these functional areas:
- Change Job
- Change Organization Assignments for Worker
You can use this task to restrict access to fields for security groups that you’ve configured on the change job business process security policy. Example: You want to hide the Pay Rate Type field from your HR Administrator security group.If you hide theClose the Current Position?field using theConfigure Optional Fieldstask, it will still display if you've configured theWhat Do You Want to do With This Person's Current Position?field in thePositionsection of the template. - (Optional) Access theChange Job Template Field Securitytab on theMaintain Functionality for Staffing Transactionstask to configure which security groups can access specific change job template fields.The field remains hidden if you’ve configuredHide for Allon theConfigure Optional Fieldstask.You can use this task to provide access to fields for any security groups, including those you haven’t configured on the change job business process security policy:
- Example: Organization A’s HR Partner is moving a worker from Organization A to Organization B. You want the HR Partner to be able to select a position in any organization, even ones they normally don’t have access to. You provide them with access to the HR Partner (Unconstrained) role-based unconstrained security group. You configure the HR Partner (Unconstrained) security group on thePositionfield on theChange Job Template Field Securitytab on theMaintain Functionality for Staffing Transactionstask. As a result, HR Partner can view and select a position in Organization B on the change job event.
- Example: You don’t want a Payroll Administrator to be able to initiate a change job event, but you want them to be able to edit thePay Rate Typefield on a change job event. You configure thePayroll Administratorsecurity group on thePay Rate Typefield on theChange Job Template Field Securitytab on theMaintain Functionality for Staffing Transactionstask.
You can also use these web services to load and retrieve the data in bulk:- Put Change Job Template Field Security Configuration
- Get Change Job Template Field Security Configurations
This feature doesn’t apply to these fields:- Effective Date
- Reason
- Location
- Which team will this person be moving to?
- Manager and Team after Change
- Who will be this person's manager after the move?
- Change Organization Assignment fields (Business Unit, Company, Cost Center, Custom Organizations, Fund, Gift, Grant, Program, Region).
- Access theActivate Pending Security Policy Changestask to confirm your changes.
Users can access different fields on a change job event based on their security access.
A manager is in these security groups:
- Manager
- HR Partner
- HR Admin
- HR Partner Unconstrained.
These security groups have access on the change job business process security policy and the
Staffing Actions: Change Job Date and Reason
and Staffing Organization: Header
domains:
- Manager
- HR Partner
- HR Admin
You configure the different security groups for different fields on the
Configure Optional Fields
and Maintain Functionality for Staffing Transactions
tasks. This table displays which fields are hidden, editable, or view-only when the manager accesses a Change Job template that includes those fields.Field | Configure Optional Fields - Hide For All | Configure Optional Fields - Hidden for | Configure Optional Fields - Not Enterable For | Configure Optional Fields - Required For | Maintain Functionality for Staffing Transactions - Change Job Template Field Security | Result |
|---|---|---|---|---|---|---|
Pay Rate Type
| Checked (True) | HR Partner Unconstrained
| Field is hidden. | |||
Position
| Manager
| HR Partner Unconstrained
| Field displayed and editable. | |||
Location
| Manager
| HR Partner
| Field is hidden. | |||
Work Shift
| Manager
| HR Partner
| HR Partner Unconstrained
| Field is not enterable. | ||
Working Time
| HR Partner
| HR Admin
| Field is not enterable. | |||
Additional Job Classifications
| HR Partner
| HR Admin
| HR Partner Unconstrained
| Field is not enterable. |
Access the
Template-Driven Business Process Security
report to confirm that the Change Job
business process and domain security permissions are aligned. You can use the
View Change Job Template Field Security Configuration
report to view the configuration for a field on these tasks:
- Maintain Change Job Templates
- Configure Optional Fields
- Maintain Functionality for Staffing Transactions