Section permissions are not enforced in a performance form.
E.g. User can read/edit a section that has section permission type 'Hidden' for that user.
SuccessFactors Performance Management
The 'Originator' (O) or 'User' (U) roles have been defined within section permissions in the xml directly. Screenshot below shows that these roles are afterwards as well visible in the UI.
The Originator and User roles cannot be granted field/section permissions. Doing so can cause errors in the field/section permissions for all other roles in the route map - for example, allowing users to see hidden sections.
Note: Attempting to grant section permissions to either of these roles in 'Manage Templates' will give an error message. Although no error message will be given if these are configured in the template XML, doing so can cause errors for all section permissions in the form.
Note: While the Originator and User roles can be used in the form route map, they cannot be granted field/section/button permissions.
performance, form, originator, user, role, section permission, field permission, custom role , KBA , LOD-SF-PM-FRM , Forms & Templates , Problem