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.

The reporting behind the article

Sources & records

Reviewed by Standards Review. Updated April 13, 2026.

  1. No Kings partners page

    Used for the official public partner roster and for a manual count of distinct partner entries on April 10, 2026.

  2. The 50501 Movement: March 28 coalition post

    Used for 50501's own description of the No Kings coalition as 'hundreds of partner organizations' and for its named examples of major institutional partners.

  3. NGP VAN / Mobilize release on March 28 turnout

    Used for the platform's claims about 3,300-plus events, 870,000-plus sign-ups, and Mobilize's role in organizing more than 90 percent of March 28 events.

  4. Mobilize Help Center: volunteer-host export

    Used for the exact fields available in a volunteer host's signup export and the fact that hosts can export signups for events they own.

  5. Mobilize Help Center: export a list of signups

    Used for the admin-level export workflow covering all signups for all events and for confirmation that hosts can export signups for their own events.

  6. Mobilize Help Center: volunteer hosts FAQs

    Used for the statement that volunteer hosts can email their event attendees and export signups before and after an event.

  7. Mobilize Help Center: permission tiers

    Used for the limitation that hosts and trusted hosts cannot access anything on Mobilize outside their own event, which narrows but does not erase the data path.