Pastoral Populations have been introduced so that schools can control who, after all other access controls are in place (confidentiality, pastoral report type), has final visibility of a report.
This can be used to broaden the criteria of which pastoral reports will be visible based upon:
- Role
- House
- Year Group
- Group
- Attribute
- Gender
Populations of users can then be pulled together into a dynamic list based upon the criteria set, for example all users that have the Role ‘Students’ that are in House ‘York’ that are in Year ‘10’ and are ‘Male’. A list of users are then displayed as belonging to this Population , users can also be explicitly excluded from the population, for example exclude any Male, Year 10, Students from York that belong to the 'Prefects’ group.
Main Menu > People Management > Populations
Select 'Create' to create a new Population. Give the Population a Label and then work through the drop down options to create the group you require.
As you work through the options, Reach will automatically show you what contacts will be included:

Once you have created your population you then apply it to the staff that you want the population to affect when they view Pastoral Reports, so for example if you want the House Parents in York House to only see Safeguarding Pastoral Report types then you apply the Population to the configuration for the members of staff that this applies to.
Main Menu > People Management > View Contacts
Find the user that you want to apply this population to, then click on the ‘Security’ tab and at the bottom of the right hand column under ‘Populations’ pick the relevant population from the drop down selection.
When the user then goes to view Pastoral Reports that are in the system, they will only see those that the selected Population allows, which in this case would be all Sage House students*

*If any other access controls are in place, such as the report is set to only be accessed by people that have ‘Confidential’ access set then these controls will be enforced before populations take effect.

Ability to see the Populations menu and create populations is determined by Infinity permissions either by set Base Security or individual permissions in the People Management permissions group:
Can the user make Populations (9-undefined, DEFINE_POPULATIONS)
Can the user see the Populations main menu item (9-183, MM_VIS_POPULATIONS)