Canvassing turfs and delivery outings reach volunteers as personal links: no account, nothing to install. To keep a forwarded or leaked link from exposing voter data, opening one takes two steps: the volunteer verifies a one-time code sent to the email or mobile on their person record, and a first-time volunteer waits for an admin to approve them. Approval happens once per volunteer, not per link. After that, every current and future assignment just works.
Approving a volunteer
When someone verifies for the first time, every admin gets an email, an in-app notification in the bell menu, and a badge on Volunteer access in the Admin section. Opening the notification takes you straight there. Each row shows the volunteer, their contact on file, and a status chip: Invited (link sent, not yet verified), Awaiting approval, Approved, or Revoked. Click Approve and their open Companion page unlocks by itself within seconds. They never re-enter a code, and the sidebar badge drops as you approve. Someone you did not expect — a stranger who scanned a QR code on a poster — can be turned away with Decline on the same row, which stops their link and clears them off the waiting list. Declining is not permanent: approve them later if you change your mind.
If you are sitting on the page while volunteers verify on their phones, Refresh at the top re-reads the list and the join code counts. New arrivals do not appear on their own.
How much a volunteer can pick for themselves
The Turf access column on an approved row decides whether that volunteer chooses their own turfs or only walks the ones you hand them. Workspace default follows the setting in Workspace → Companion apps. Any turf in campaign lets them open the turf picker in the Canvass Companion and start on any turf that isn’t retired — including one somebody else is already walking, which is how a group splits a turf. Only assigned turfs pins them to what you place them on. Changing it takes effect on their next tap; nothing needs resending.
A volunteer you’ve never placed on a turf can still pick one, as long as they may roam. They see the turfs of every campaign that isn’t archived, unless they joined by scanning a QR code for one campaign, in which case they see that campaign’s turfs. Once they’re on a turf, roaming keeps them inside the campaigns they’re actually working.
Revoking access
Revoke signs the volunteer out of every phone they ever verified, effective on their next request, and dead-ends their links. Use it when someone leaves the campaign or a phone is lost. You can approve them again later. They’ll verify a fresh code first. Every approval and revocation is recorded in the activity log.
Verification needs a contact on file
Codes go to the email or mobile number on the volunteer’s person record. If neither is on file, the link tells them to ask you. Add a contact to their record and have them reopen the link. Merging two volunteers keeps only one volunteer record
A person can hold one volunteer record, so merging two people who both have one keeps the record you are keeping and removes the other, along with the phones signed in on it. If the removed one was the approved record, that volunteer verifies a code again and needs approving again. The merge confirmation says this before you commit, and only when both people are volunteers. See Find and merge duplicates. 