Settings and configuration

pplCRM separates what affects you from what affects everyone. Settings (avatar menu → Settings) opens a compact popup for your personal preferences and applies every change instantly. There is nothing to save. The Workspace settings (administrators only, under Admin in the sidebar) set policy for everyone and use a deliberate Save with a leave-guard.

What lives in your Settings popup

• Notifications: a per-event matrix of email and in-app switches (mentions, task assigned, tasks due, person assigned, export ready, import summary). Each toggle saves as you flip it.
• Appearance: Theme is Light, Dark, or System (follows your device’s setting), applied live.
• Passkeys: the devices that can sign you in; add one with your device prompt, or remove one you no longer trust.

What lives in the Workspace settings

• Organization: your name, contact details, and mailing address.
• App: how the volunteer-facing apps behave, including whether volunteer route links expire after 30 days. Expiry is the secure default (a forwarded or long-lost link goes dead on its own), but you can turn it off if your delivery routes run longer. Volunteers still verify a code and need a one-time approval either way.
• Communications: default from-name and from-address (verified senders only), reply-to, the newsletter footer disclaimer, and double opt-in for web-form subscribers.
• Notifications: workspace-wide notification defaults (individuals refine their own on their profile).
• Teams & access: default role for invitations and the MFA requirement.
• Service levels: response-time targets for email and tasks, working days and hours, and the warning/critical thresholds behind the dashboard status.
• Appearance: default theme and date format for the workspace.
• Integrations & API: webhook keys and connected services.
• Billing: your plan, live usage, and payment details.

Plans and billing

pplCRM has three feature tiers: Free, Grassroots, and Movement. Which tier you are on decides which features you have. Within a paid tier, the price scales smoothly with your emailable-subscriber count instead of jumping between price points, so growing your list never means a sudden shock to the bill.

• Free: $0 forever. Up to 1,000 emailable subscribers, 2,000 emails a month, 2 staff seats, and 1 GB of storage. Includes the full people CRM and newsletters. No companion volunteers.
• Grassroots: starts at $29 a month for up to 1,000 emailable subscribers, then rises in steps as your list grows, up to $359 a month at its 100,000-subscriber ceiling. Adds web forms, donations, automations, lists, and volunteer management (teams and events).
• Movement: starts at $55 a month for up to 1,000 emailable subscribers, then rises in steps up to $665 a month at its 200,000-subscriber ceiling. Adds the canvassing and deliveries companion apps with unlimited companion volunteers: turf cutting, walk lists and routes, field reports, yard signs, and route optimization, plus A/B testing and priority support.
• Enterprise: for federations, parties, and multi-office operations with custom needs. Pricing is negotiated directly. Reach out from the Billing page.

Every plan meters emailable subscribers, not total contacts. Your whole voter or canvassing universe stays free to store; you only pay for the people you can actually email.

Plan prices exclude tax. Where your jurisdiction requires it, sales tax, VAT, or GST is calculated and added at checkout based on the billing address you enter there, and appears as its own line on every invoice and receipt. If your organization has a business tax number (VAT, GST, or similar), you can enter it at checkout so it appears on your invoices and any business-to-business tax treatment applies automatically.

What happens when your list grows or shrinks

When your emailable-subscriber count crosses into a higher price bracket, every admin and owner is notified, and the new amount takes effect on your next billing cycle, never mid-cycle. If your list shrinks back below a bracket, the lower price also reconciles at the next cycle boundary rather than refunding the current one.