Canvassing teams
How to organize canvassers into teams with leads and members, so you can delegate management without making everyone an org admin.
Teams let you hand off day-to-day canvassing management to a trusted organizer without giving that person access to the rest of your workspace. A team lead can add volunteers, adjust roles, and reassign territories and walk lists within their own team. They cannot touch resources outside it. Org admins retain full access everywhere.
Teams are optional. If your org does not use them, territories and walk lists behave exactly as described in Canvassing: only the assigned volunteer and org admins can act on a resource.
Creating a team
Only org owners and admins can create teams. Open Canvassing in the workspace sidebar, select Teams, and click New team. Give the team a name and an optional description.
You can optionally place the new team under a parent. A lead on the parent gains lead-level rights over all descendant teams; that cascade does not apply to members.
Team roles
Each person on a team holds one of two roles.
| Role | What they can do |
|---|---|
| Lead | Add or remove members, change member roles, assign or reassign the team's territories and walk lists. Reassignment is limited to other members of the same team. |
| Member | See all territories and walk lists owned by the team. Act only on resources assigned to them personally. |
A team must always have at least one lead. The system will not let you remove the last lead while other members remain.
Any active org member can be added to a team. Members receive an in-app notification when they are added, removed, or promoted to lead.
A lead cannot move a territory or walk list to a different team, create child teams, or reassign a resource to someone outside the team without first adding them (the reassign dialog offers an add-and-reassign option in one step). Org admins bypass the same-team rule and can move resources between teams or assign to any member across the org.
Nested teams
Teams can nest to any depth. A lead on a parent team holds lead-level rights over every descendant team. Being a member of a parent team does not make you a member of a child team; membership is not inherited downward. The team list page shows the full tree with member, territory, and walk list counts for each team.
Team-scoped resources
Territories and walk lists can each belong to a team. A resource without a team remains in the flat model: only its assignee and org admins can act on it. The Work tab on a team's detail page lists every territory and walk list the team owns.
Removing a team
Only org admins can delete a team. When a team is deleted, its territories, walk lists, and child teams roll up to the deleted team's parent. If the deleted team had no parent, its resources become teamless and its child teams become top-level teams.
Why this matters
Without teams, every canvassing management task falls to an org admin, which either creates a bottleneck or forces you to grant admin rights more broadly than you should. Teams let you match authority to responsibility: a trusted lead manages their own group without touching anything else in your workspace. As your program grows, nested teams let you scale that same pattern across regions, chapters, or campaigns while keeping each lead's scope well-defined. You stay in control of the overall structure; your leads handle the day-to-day.