Campaigns and contexts

Your workspace always has one permanent office context, the constituency office’s day-to-day home. When an election comes, an administrator creates an election campaign alongside it under Workspace → Campaigns. People, households, and companies are shared across every context: one contact list, no duplicates. What stays separate per campaign is what you learn and are permitted to do in it: supporter data, email consent, and outreach.

Each campaign declares what it is running for

A campaign also records the office it is contesting: the country, the level of government, the province or state, and the seat. That is what makes the app say riding to an Ottawa campaign, constituency to an Alberta one, ward to a Toronto councillor and congressional district to an Ohio campaign — on the same screens, without anybody configuring wording. It also decides which boundary maps your households are matched against. Two campaigns in one workspace can be at completely different levels, and a household holds the areas for both at once. See What office a campaign is running for.

Who works in which campaign

Campaign membership is an admin decision, not a personal choice. Editors and Viewers belong to exactly one campaign: the one an admin assigned them to on the Users page or in the invite dialog (unassigned members work in the office). Everything they see and do — newsletters, forms, donations, canvassing, the inbox — stays inside that campaign, and their Profile shows which campaign they are part of. Admins and owners can work in every campaign: they pick the context they are currently working in from Workspace → Campaigns (Work in this campaign), and that choice is theirs alone and follows them across devices.

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, users assigned to it move back to the office context, and you can unarchive if late data needs to be entered.