Imported contact restrictions and removing a constituent

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.

Confirm which volunteer interface and import configuration the school uses. Legacy VMS can store school-specific constituent values in its data fields. The newer import mapping recognizes restrictions/solicit-code inputs as Person solicit-code records. Receiving a CRM column is not, by itself, proof that the intended sending restriction was mapped and enforced in the affected workflow.

For an unexpected solicitation, ask support to trace the source column and value, latest successful import, active unit, volunteer role/assignment, and actual outbound message and recipient. The legacy email list uses assigned constituents with a preferred email, and sends to that address. Confirm that a CRM restriction is mapped to an enforced email restriction rather than only a visible note. Do not assume that “No Student Calling” universally suppresses email, or that a display note is an enforced opt-out. Confirm downstream suppression and the school's mapping before identifying the cause.

Removing an assignment is different from removing the constituent or setting a communication preference. The constituent deletion CSV workflow invokes removal with imported-gift deletion enabled; associated VMS assignments, notes and other constituent data can also be removed. It is not a simple unsubscribe control and does not itself establish that a future import will exclude the person. Review the intended suppression and data-retention outcome with support instead of recommending constituent deletion as a routine email-preference fix.