Any recruiting operator is not able to move candidates to any status of the talent pipeline. When a user tries to move an applicant in the Candidate Pipeline, the system displays a pop-up error box with the following error message "You do not have permission to change the candidate status" every time.
The 'statusId' field is not defined in the application template; or the field has not been granted correct permissions in the template.
It is very important to define the 'statusId', 'resume', and 'application comments permissions' fields in the Candidate Application template.
If you are using Single Stage Application, the permissions in the Application template will be reflected.
If you are using Multi Stage Application, all field-permissions in the Application XML should be commented out or removed except the write permissions to the 'statusId', 'resume', and 'application comments permissions' fields. If permission to 'statusId' is not maintained in the Application template, then users will not be able to move candidates across the talent pipeline. All other field permissions should be defined in the Requisition template, including the 'coverLetter' field.
If contradicting field permissions are specified in both the Application and Requisition templates, the permissions may not be rendered correctly for recruiting users.
KBA , LOD-SF-RCM-APP , Applicants and Job Applications , Problem