There are 4 options to restrict the target population of the Position object. You can restrict the target population of a position on a role-based on position attributes, position relationships, and the position hierarchy.
To set restrictions, you need to navigate to Manage Permission Roles and select the role of your choice. Locate and select the Assignments tab, and on the Actions, select Edit.
In the next step, you can select 4. Define Target Criteria and scroll down to Miscellaneous Permissions. Locate the Position object, and select the radio button Restrict Target Criteria to:
Four possible options will become available:
- By field criteria ("Include access to Position with the following criteria" option). As an example, you could restrict the target population of the Position object to positions that belong to a specific Company and Departments. You can use different operators
- Equals to (=). As an example, include access to Positions within the company Ace_USA
- Is not Equal to (!=). The opposite case to include access to Positions from all companies except Ace_USA
- Is null (if a value of a field is empty).
- Is not null (if a value of a field is not empty)
- In (in). This option allows a multiple selection (as an example, we could select several Departments to include access)
- To positions in the hierarchy below the granted user's position ("Include access to Position in the hierarchy below the Granted User's Position" option.) Example : Restrict the target population of the Position object to positions 2 levels below the Granted User’s Position. For this particular option, access is given based on the Parent Position.
- Parent Position = 1,2,3 or all level(s) down . Which means that, if you select Parent Position = 2 level(s) down, role will have access to all the positions 1 level below their own position.
- To positions with Matrix Relationship to the granted user’s position ("Include access to positions that have the specified type of association with the granted user's position" option). This option works similarly to granting permissions to a user’s matrix reports, but it is based on the Matrix Relationship from the Position object ("positionMatrixRelationship" association).
- To positions in the hierarchy below a given position ("Include access to Position in the hierarchy below Position with the following criteria " option). This option will restrict target population based on a specific Position Code + Parent Position hierarchy. In this example, users that have this permission role granted would have access to all positions 1 level down from the specific position with Code Pos_ID7
- Code = Pos_ID7
- Parent Position=2 level(s) down.
Additionally, you can choose to Exclude access to Granted User's Position. Whenever any of the above options to restrict target population for Position object are into effect, this checkbox would also exclude the access to granted user's own position.