WHYAMERICASUCKS.COM
PUBLIC SITE MAPLatest Stories
menuMenu
No Kings protesters lined a roadside with flags and signs in Aurora, Colorado
Coalition Stack Story

No Kings Ran Through Hundreds Of Partners And Exportable RSVP Data

No Kings listed hundreds of partner groups and routed event organizing through Mobilize. Mobilize help docs say hosts and admins can export RSVP data and contact attendees after signups.

Published
April 10, 2026

Records Research Desk

Updated
April 13, 2026

Standards Review

Investigation
Mind Control

Official partner pages + Mobilize help docs

Byline

Records Research Desk

Reviewed By

Standards Review

No KingsMobilizeIndivisible50501ProtestsData Collection
Mind ControlRecords Research DeskStandards Review8 min read

The coalition was large enough to function like infrastructure

A manual review of distinct partner logo files on the official No Kings partners page on April 10 found at least 368 listed partners or formations, excluding No Kings branding assets.

50501's March 28 coalition post described No Kings as a coalition of 'hundreds of partner organizations' and named AFL-CIO, Indivisible, NEA, Planned Parenthood Action Fund, Public Citizen, SEIU, and MoveOn.

The partner page shows multiple currents inside one apparatus

The page includes labor formations, Democratic clubs, climate groups, Women's March organizations, 50501 affiliates, and at least 18 Indivisible-branded entries by our review. It also includes groups such as 73 for Palestine and Jewish Voice for Peace.

A coalition this broad requires partner intake, event campaigns, host approvals, communications flows, and a way to keep thousands of local actions moving under a national umbrella. Mobilize supplied the event layer.

At that scale, RSVP collection becomes operating infrastructure

A 20-person rally page and a coalition with hundreds of partner groups do not present the same data question. Once a campaign reaches this size, RSVP collection becomes part of the operating system that helps organizers recruit, segment, follow up, and keep local actions tied to a national brand.

Mobilize's export rules answer the practical question. Once sign-up data is portable, organizers can keep working attendee lists after the event.

Mobilize's host workflow makes the data path operational, not theoretical

One article says volunteer hosts can export signups for upcoming and past events they own. Mobilize says each signup row in that CSV can include name, email, phone, zip code, event, attendance status, event type, affiliated organization, sign-up sources, and post-shift feedback if applicable.

Another Mobilize help article says admins can export all signups for all events from the dashboard's Exports tab, while hosts can export signups for their own events. A separate volunteer-host FAQ says hosts can email their event attendees from the event details page and can export signups before and after an event.

The platform also narrows who can see what

There is one important limit worth keeping. Mobilize's permission-tier documentation says hosts and trusted hosts cannot see or edit anything on the platform outside their own event. The data access path is not a free-for-all across the entire network. A local host does not automatically get a national dashboard.

The limit narrows the access path. No Kings still used a platform where event-level hosts can export and message their own signups, while organizations and admins can work with larger pools of event data across their dashboards.

More Stories

Keep Reading

These related pieces come from the same public-records layer, but follow different investigations and reporting paths.