Assignments can override cohort visibility exclusions

For the established (legacy) Volunteer Management portal. These steps differ from the newer Volunteer Management interface. Administrator controls require the appropriate school or volunteer-management permissions.

Use cohort-based role visibility to separate Class Officer and Class Agent access, but exclusion from a role query is not a hard deny: explicitly assigned constituents are added back to searchable constituents, and assignment independently grants constituent access. Therefore remove Do Not Solicit constituents from Class Agent assignments, review all of each volunteer’s roles and any see-all access, and test assigned as well as unassigned examples. Authorized administrators can configure cohorts in Manage Volunteers; Support is useful for reviewing the design rather than always required for cohort creation. Use an existing mapped solicit-code or other supported structured field where possible. A new upload column is needed only if the relevant value is not already imported, and its import mapping must be configured. A visibility cohort alone must not be represented as an absolute solicitation prohibition.