Getting started

Field OP is where a campaign keeps the people it talks to and runs the work of talking to them. Managers work in this console; volunteers knock doors with the Field OP app on a phone. This page is the first half hour: how you sign in, how your organization came to exist, how everybody else gets in, and what each role can do.

Signing in

Use the link your campaign sent you. The sign-in page needs to know which campaign you are signing in to, and it cannot work that out on its own — that is deliberate. A "which campaign are you with?" list would tell anybody who asked which campaigns are here. The address your invitation came from carries it, and so does the standing sign-in link an administrator can send you. With no campaign in the address, the page says so and offers no box at all.

The first time, open the link in your invitation e-mail. It is your invitation: it works once, for the address it was sent to and no other, and it stops working when the invitation expires — so do not forward it. Open it in the browser you will sign in with; the page says "Your invitation is ready in this browser" and takes the link out of the address bar. Then sign in with the address the invitation was sent to, and the invitation is accepted as you do. If you are asked to open the link again, it is because this browser does not have it: open the e-mail on this computer, or ask whoever invited you to send it again (a new invitation replaces the old one and its link).

Once you are at your campaign's sign-in page, there are four ways in:

Your e-mail and password, once you have chosen one. At least twelve characters; a phrase you will remember beats a complicated word, and there are no other rules. New here? Choose your password e-mails a link to choose your first one: your invitation made your account, with no password, and nobody but whoever reads that mailbox can give it one. There is no "create an account" here.
A one-time link. "E-mail me a sign-in link instead" sends a link that works once and expires in an hour. No password needed.
Continue with Google or Continue with Microsoft, if your campaign has them switched on. If it has not, the page says so and points you at the other two. Google signs you in to the account your invitation made when it vouches for the same address; Microsoft does not vouch for addresses, so for an account made by an invitation use the link or a password instead.

"Forgot password?" sends a reset link. Whether an address has an account here is never revealed by the answer — the page says the same thing either way, and so does "Choose your password".

If a link does not arrive within a minute or two, look in the spam folder before asking for another: a second link makes the first one stop working.

Your campaign may require two-step verification of its administrators, and then also of anyone holding a Restricted Data, Export or Permanent deletion grant. You set it up under Settings → Two-step verification with an authenticator app — in the console, or in the phone app's own Settings — and after that you are asked for a code when you sign in.

The first time you sign in, Field OP shows you what the platform holds about you — the person, not the campaign's records. Read it and press Continue. It is shown once, it is not a gate, and nothing is refused if you never read it.

How an organization comes to exist

Two ways, and no others.

Somebody signs up and pays. They prove an e-mail address, name the organization, pick a plan, give the election day and pay on Stripe's own page. Field OP then makes the organization and its first administrator, and sends that administrator a welcome message with a sign-in link; the first campaign is made from the console once they are in. An organization in Québec cannot sign up this way yet. Québec's privacy law (Law 25) and its language law call for a privacy impact assessment and French versions of the documents a customer agrees to, and that work is not finished. The sign-up page says so, in English and in French, as soon as Québec is chosen; it saves no sign-up and charges nothing, and offers a message to info@fieldop.ca instead.
Gestalt provisions it, for organizations that are set up by arrangement rather than by card.

Either way the result is the same: one tenant administrator who has never signed in, holding an invitation. Everybody else in the organization is invited by somebody already in it. There is no other door — adding an account on Google's side does not make a Field OP account, and the platform will still refuse it.

Inviting the rest of the campaign

Admin → Who can sign in → Invite somebody. One address, one role, and the invitation is good for seven days. Field OP mails the person their own invitation link — you never see it, so nobody can be handed somebody else's — and when they open it and sign in with that address, the invitation is spent. Inviting the same address again sends a new link and the old one stops working; that is also the way to re-send an invitation that was issued before 10 October 2026, which has no link and can no longer be accepted. You can say what to call them; that name is how the campaign's staff see them on every roster, and nobody outside your organization sees it. The Members list on the same screen lets you give, correct or clear a name later.

Every role except Administrator is held on one campaign, so the form asks which. An Administrator is the whole organization's and has no campaign to name — choose that role and the question disappears.

The same screen lists the invitations that are out, with their state, and lets you revoke one that is still pending. It is also where you send a member a password-reset link — which goes to their own address and is never shown to you — and where an administrator requires two-step verification of every administrator and of everyone holding Restricted Data, Export or Permanent deletion. You have to have it on your own account before you can require it of others. Requiring it is one press; making it optional again says first what that gives up and asks you to confirm it is you — if your sign-in is more than five minutes old, sign out, sign in again and press it within five minutes — because it loosens every administrator's sign-in at once. Inviting another Tenant administrator asks you to confirm it is you first, because an administrator can approve the most dangerous grants.

A tenant administrator who is setting the organization up for the first time gets a checklist on Home: confirm the organization's name and time zone, create the first campaign, import the list, invite the people who run it, draw the ground, plan the first canvass, and install the phone app. Each step links to where it is done, and the panel disappears when it is finished.

The roles, in a paragraph each

A role is what somebody may do. It is always held on a scope — the organization, or one campaign — and the narrower one wins where they overlap.

Administrator — the organization itself: who may sign in, what roles they hold, who holds a dangerous power, billing, the organization's settings, and its tags. Administrators can also read and correct a person's record, because an administrator who can see nobody cannot look into a complaint about how the campaign handled somebody's data. Restricted information is still a separate, time-boxed grant.
Campaign Manager — full operational reach across one campaign: people, universes, turf, canvasses, missions, shifts and the numbers. Exporting and restricted information are grants, not part of the role.
Field Lead — the same operational reach, for the field work of a campaign.
Organizer — the Field Lead's reach, narrowed by geography, team or list.
Data Steward — import, identity resolution and merging duplicates. Only a Data Steward runs an import. Export is a grant.
Captain — a team's roster and its assignments: watch, help and reassign inside their own scope.
Volunteer — their assigned mission and nothing else. They record conversations, and they start and finish their own walk. They see no scores, no inferred labels and no restricted notes, ever, by any path.
Candidate — progress, coverage, priority areas and their own follow-up queue. No administration, no bulk data, no exports.
Observer — read-only, inside an explicit scope.

Powers that are never part of a role

Some things are dangerous enough that no role carries them. They are grants: named, given to one person, and several of them expire on a date. Taking data out of the platform, deleting something for good, publishing content or an action, approving legal wording, configuring the intelligence features, sending outreach, handling finance, reading restricted information, working as an outside collaborator, and letting a candidate correct a person's record are all grants. An administrator issues and revokes them under Admin → Access, where you can also see who holds what today.

Four of them — Restricted details, Export, Permanent deletion and Edit people — also need a second administrator's approval. The administrator issuing one chooses who to ask, that person is told by e-mail, and the grant does nothing until an administrator who is neither the issuer nor the holder presses Approve on the Access screen and confirms it is them. A request nobody approves within three days lapses.

Around the console

The rail down the left is the areas: Home, People, Organize, Field, Work, Insights and Admin, with Settings and this help at the foot. Every area is offered and the platform decides what is behind it — a door you would only be refused is not shown to you at all, so what you see in the rail is what you can actually use.

Your own work. If you have field work of your own — a person record in the campaign, or a mission — the rail also offers My missions, Shifts I was asked to and Check in or ask for help. They open the Field OP app in this same browser, with the same sign-in, because that is where a walk, a shift answer and the safety buttons live; nothing about them is drawn twice. Somebody with no field work of their own is not offered them.

On a phone the rail becomes a bar along the bottom: the first four areas, and More for everything else — the rest of the areas, your own work, every Admin screen you may use, Settings, this help and Sign out. Long lists such as People and Export show each record as a card, and wide tables scroll inside their own box rather than pushing the page sideways.

Every feature is coming to every surface. The Field OP app gains the console's screens area by area, under its own More, and the console reaches the volunteer's screens through the app. What never goes onto a phone-sized screen — a full date of birth, sex or gender, restricted notes, an import's restricted columns — is shown only in the console on a computer or a tablet, whoever you are.

Putting the console on your home screen. On an iPhone, open the console in Safari, tap Share, then Add to Home Screen. On Android, open it in Chrome and choose Install app (or Add to Home screen) from the menu. It then opens in its own window, like an app. It keeps none of your campaign's records on the phone: without a connection it shows a page saying so, and when a new version of the console is ready it asks before reloading — save what you are working on first. If you close every console window instead, the new version is simply there the next time you open it.

If your organization is behind on a payment, or is closing, a banner says so on every screen before you press anything. Billing and plans explains what each standing means.

Next: People and imports · Field · The phone · Getting help