Manage volunteer templates, versions, and communications

For the newer Volunteer Management interface. Access and available actions depend on your volunteer or administrator role.

How to use

In the newer administrator portal, open Outreach → Outreach Hub for constituent-facing templates used by volunteers. Open Volunteers → Communicate with Volunteers for administrator-to-volunteer templates. These libraries have different sender/recipient contexts; choose the one matching the message audience.

The administrator template libraries expose create/edit, duplicate, archive, restore, permanent deletion, version history, and revert actions. Use test-email and merge-token preview to check the message in the correct context. The separate email-volunteers action sends composed content to the selected volunteers.

Troubleshooting

An archived template and a permanently deleted template are different outcomes. Inspect the archived library before recreating a missing template. A merge field that works when the volunteer is the sender may differ when the volunteer is the recipient.

Account-specific settings

You should not expect that reverting a template changes messages already sent.

Email volunteers their individual campaign advocate links

1. In the Volunteer Management administrator portal → Volunteers, select the volunteers and choose Email Volunteers. Review whether you selected specific rows or all matching volunteers before including the entire roster.
2. In the composer toolbar, open the link picker, choose the campaign and its Advocacy option, then insert the advocate link into the email content. You can also insert available Giving Form or event links from the picker.
3. Review the message and recipients, then send. Each eligible recipient volunteer receives their own advocate link; you do not need to sign in as each volunteer to copy links manually.

The administrator-to-volunteer template library remains Volunteers → Communicate with Volunteers. Constituent-facing templates used by volunteers remain under Outreach → Outreach Hub. Choose the correct audience: the same advocate placeholder resolves to the sender for constituent outreach and to each volunteer recipient for an administrator-to-volunteer email.

Superadmin, Volunteer Management Superadmin and Volunteer Management Admin include administrator messaging of volunteers. A reporting-only staff role does not grant that send action. This does not change the configurable email capabilities of volunteer roles.

The link identifies the sending volunteer when the audience is constituents. In an administrator email to volunteers, it identifies each recipient volunteer, not one shared administrator advocate. A Pending volunteer without a linked GiveCampus account cannot receive a personal attributed link in that send: the fallback is the plain campaign page with no advocate credit. Have the volunteer link their account first when individual attribution is required.

The editor may contain an $Advocate_URL[campaign ID]$ placeholder. The send resolves it to the appropriate volunteer's link. A preview may substitute a general campaign URL, so preview alone does not prove personalized attribution. Do not replace the placeholder with one copied person's link for everyone.

For campaigns on the newer advocacy experience, the sending volunteer is enrolled for campaign advocacy; display on advocate lists/leaderboards can depend on tracked activity. An administrator-to-volunteer send does not immediately enroll every recipient merely by sending the email; the recipient's link activity handles enrollment. Campaigns on the older advocacy experience can still credit gifts from an existing advocate link but do not list the volunteer as a campaign advocate through this flow. The current picker offers Advocacy for campaigns on the newer experience; a missing Advocacy option on an older campaign is not a missing VM email permission.

Volunteer advocate-click and dollars-raised reporting inside VM is not yet available. Do not promise an in-VM advocacy analytics screen. These are VM email instructions, not the GC Outreach autofill CSV workflow.