Campaigns and contexts
One shared contact list, separate campaign workspaces: how the office and election campaigns coexist without mixing supporter data.
2 min read
Switching contexts
What is separate per campaign
Support level: Strong, Leaning, Neutral, Leaning against, Against, Undecided; “Unknown” simply means never asked. Someone can back your office work and oppose the campaign, or vice versa. Voting status: Will vote, Voted (advance or election day), Not voting, Ineligible. Once someone has voted in advance they drop out of later call and knock lists. Email consent: subscribing to the office newsletter is not consent for campaign email, and unsubscribing from one never touches the other. A hard bounce or spam complaint suppresses the address everywhere, and do-not-contact on a person overrides every context. Newsletters, donations, forms, lists, events, canvassing turfs, and deliveries: each belongs to the context it was created in, so campaign funds and office funds never mix. The Inbox and its email connection: each campaign connects its own Office 365 or Gmail account and has its own Inbox. Switching context switches both the connected mailbox and the mail you see; connecting an account under one campaign never affects another. See The shared inbox.
Campaign lifecycle
Create a campaign before the race, with a start date and election day. Carry over support levels from the office or a previous campaign as a starting assumption. Email subscriptions copy only behind an explicit confirmation. Consent judgment stays with you. Voting status never carries over. Work in it during the campaign. Data recorded there never bleeds into the office. Archive it after the race: everything stays viewable as read-only history, and you can unarchive if late data needs to be entered.
Try this on sample data.
Every feature in the docs is live in the free demo workspace — no card, nothing to lose.
Start free