Volunteer coordination

It is three connected screens. Team (`/dashboard/<campaign>/team`) lists every member with their role, walk count, and last active date, plus tabs for pending email invites and share links. My profile lets each member record a phone number, languages, vehicle access, comfort level, and neighborhoods they know. Leaderboard ranks everyone by doors knocked and signs logged and awards badges.

Membership is per campaign. One account can own a school board race, be an admin on a county party, and volunteer for a neighbor's city council run at the same time; the campaign switcher in the sidebar moves between them. Each membership carries its own role, and nothing crosses between campaigns.

Every membership has one of five roles. The table shows what each can reach; row-level security enforces the same boundaries underneath the app.

Role changes are tiered. Owners and Admins can change a Staff or Volunteer role. Changing an Admin's role requires the Owner, except on group campaigns (PAC, party, coalition) with no owner member, where Admins may change each other. The Owner role never changes from the menu; instead an Admin can be promoted with Make candidate, which demotes the current owner to Admin so there is always exactly one owner.

There are two ways to add people. Invite by email sends one person a link tied to their address. You pick the role, optionally their name, an expiry from 1 to 365 days (14 by default), an internal note only staff see, and optionally a walk to attach. New share link creates a URL anyone can use to join at a role you choose, with an optional maximum number of uses (up to 10,000), an optional expiry, and again an optional walk.

The link lands on `/invite/<token>`. Someone already signed in sees Accept or Decline; someone new creates an account or signs in to an existing one. Email invites are bound to the invited address, so the link cannot register a different email. Accepting creates the membership, and if a walk was attached it also creates the walk assignment, so the walker lands in that walk on first sign-in.

Invites for volunteers and precinct chairs include install links for the iPhone and Android app. Managers can also use Get the app to copy those links or Send app invite on any member. Pending email invites can be copied, resent, or canceled; share links show how many people joined and are marked expired, exhausted, or canceled when they stop working. A precinct chair can invite too, but only volunteers, and only into their own precinct.

Each member edits their own profile at My profile: a phone number (stored normalized so organizers can reach them), languages spoken (13 common languages plus free text), vehicle access (yes, no, or skip), a comfort level (door knocking, phone only, or either), and neighborhoods they know well. Neighborhood suggestions come from the neighborhood values in your voter data, highest voter count first.

There is no shift calendar or availability grid. Comfort level and vehicle access are the capacity signals the product stores; for scheduled shifts, use Events with sign-ups and capacity.

Walk assignments are made on the walk itself or by attaching a walk to an invite. Clicking a member on Team opens an activity panel: doors knocked, surveys captured, signs credited, last active, a per-walk breakdown with assigned, started, and completed times, badges earned, and a timeline of the last 25 actions. Counts come from an activity ledger, so a stop mirrored from a joint canvass is never double-credited and a six-question survey counts once.

For Staff, Owners and Admins open Edit permissions and grant access by bucket: Voters (view, export lists, annotate), Outreach (view, create, send), Walks (view, participate, create, edit, delete, assign), Events, Leaderboard, Fundraising, Social, and Volunteers. Granting any voter permission unlocks the voter, query, lists, and tags pages, and the sidebar updates immediately. Reset returns the person to the staff default.

The leaderboard ranks members by doors knocked plus signs logged, with recorded responses as the tiebreaker. Every member sees their own card: doors knocked, signs logged, walks completed, rank out of everyone ranked, and progress toward the next badge. Door badges: First Steps (1 door), Star Walker (10), Half Century (50), Centurion (100), Iron Walker (250), Legend (500). Response badges: Conversation Starter (1), Listener (25), Field Whisperer (100). Signs credited count both your signs placed and opposition signs reported.

Privacy is per campaign and set by each person: full name, first initial plus last name, a custom alias, or anonymous, and they can hide themselves from other volunteers entirely; staff still see everyone for coordination. Staff and above can click any row for that person's walk-by-walk history, while volunteers see the plain board.

Remove from team asks twice: once to confirm, once to decide whether to revoke their walk assignments (recommended). Removal is a soft delete: the membership row is stamped with who removed it and when, the person disappears from the Team list, and the helper every access check runs through ignores removed rows. Their door knocks and survey responses stay in your data, marked as removed. A removed precinct chair loses their export grant immediately.

Isolation is enforced at the database. Every campaign-scoped table has a campaign column and a row-level security policy that checks membership and role before a row can be read or written. A volunteer who walks for two campaigns has two memberships in two workspaces and sees nothing across them. When the race ends, an Owner or Admin can archive the campaign: reads stay open for the team, every write is rejected, and any admin can reactivate.

School board, one organizer, no paid staff. You post a share link in a neighborhood Facebook group with 25 maximum uses and a 30-day expiry. Twelve people join and install the app from the invite email. You assign the four who marked door knocking to generated walks and put the phone-only volunteers on a phone bank. Two Saturdays of four walkers at roughly 40 doors each is about 320 doors, and the leaderboard shows who did what.

City council with a field director and two canvassers. You invite the field director by email as Admin. The two paid canvassers come in as Staff with the defaults: walks, team, leaderboard, events, no voter export. A part-time data volunteer is Staff with View voter records granted, so she can build lists but still cannot download a CSV. When a canvasser leaves mid-cycle, you remove him, revoke his walks, and his access ends that minute.

County party with 30 precinct chairs. On a party-type campaign, you invite each chair by email with their precinct number. Each chair sees their own precinct's voters and walks, invites volunteers with a share link automatically scoped to that precinct, and sees only their cohort on Team. You grant CSV export to the three chairs who run their own mail, and nobody else can pull a file.

Local races are won by contact, and contact is done by people. The research in the door-knocking guide is clear that in-person conversations move turnout more than paid media, but only if someone knocks the doors. Taking a volunteer from a link to a phone with a walk attached removes the step where most are lost.

The margin in a local race is often a few hundred votes. Working out how many votes you need tells you how many doors that is, and the leaderboard tells you whether they are getting knocked. For county parties, the precinct chair role puts a scoped tool in the hands of the people the party already depends on; the precinct chair explainer covers that job.

Honest limits, so you can plan around them.

• No shift scheduling or availability calendar. Use Events with capacity for shifts.
• No cross-campaign volunteer pool. Each campaign recruits its own people, even when the same person volunteers for both.
• Volunteer access cannot be widened. To give someone more, change their role to Staff.
• The Precinct Chair role exists only on PAC, party, and coalition campaigns, not on an individual candidate's campaign.
• No embeddable sign-up widget for your own website yet; use the join page or a share link.
• Invites and app links go by email; there is no SMS invite to volunteers.
• Paired walking (two walkers surveying the same door) is not supported; multiple walkers on one walk split the doors.

Volunteer coordination is the people layer for the rest of the field stack.

• Block walking: assign walks, attach a walk to an invite, and let volunteers claim open walks.
• Volunteer mobile app: where volunteers see assignments, knock doors, and capture surveys.
• Events: sign-ups, reminders, and GPS check-in for phone banks, canvass kickoffs, and rallies.
• Precinct chair tools: the scoped precinct view, chair-created walks, and the export grant.
• Yard signs and field assets: signs placed and opposition signs reported count on the leaderboard.
• Campaign page: the public join page where supporters first raise their hand.