The coalition was even bigger than the first pass suggested
The first No Kings story established that the protest was organized, not leaderless. The next layer is scale. 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. That is not a ragged handful of groups sharing a hashtag. It is a very large coalition stack with enough formal infrastructure to look more like a campaign ecosystem than an improvised civic flare-up.
50501's own March 28 coalition post points in the same direction. It described No Kings as a coalition of 'hundreds of partner organizations' and named major institutions such as AFL-CIO, Indivisible, NEA, Planned Parenthood Action Fund, Public Citizen, SEIU, and MoveOn. So even before anyone argues about donor money, the movement's own public-facing material already shows a serious national apparatus.
The partner page is not ideologically narrow in the simple way critics claim
That official roster also helps sort signal from noise. 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. But it also includes groups such as 73 for Palestine and Jewish Voice for Peace. That means the coalition is neither a purely spontaneous anti-Trump mass nor a perfectly sterilized one-note brand. It is a broad progressive alliance with multiple currents sharing the same infrastructure.
That nuance matters because it strengthens, rather than weakens, the institutional story. A coalition this broad has to be managed. It needs partner intake, event campaigns, host approvals, communications flows, and a way to keep thousands of local actions moving under a national umbrella. That is exactly where Mobilize comes in.
Mobilize's host workflow makes the data path operational, not theoretical
The strongest new documentation comes from Mobilize's own help center. One article says volunteer hosts can export signups for upcoming and past events that 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. That is much more concrete than the generic privacy-policy language people usually stop at.
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. In other words, RSVP data is not just stored. It is designed to be actionable at both the host and organization level.
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. That means the data access path is not a free-for-all across the entire network. A local host does not automatically get a national dashboard.
But that limitation does not erase the core concern. It simply clarifies it. The more accurate statement is that No Kings 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. That is still a significant participation-data structure.
What this sharper record does and does not prove
This follow-up still does not prove a covert federal dissident registry, a biometric harvesting scheme, or a secret law-enforcement trap. I have not found public evidence that the No Kings coalition or Mobilize was doing that. Those claims need a different order of proof than the current record provides.
What the current record does prove is strong enough on its own. No Kings ran through a coalition that publicly described itself in the hundreds, and the event stack gave organizers and hosts practical tools to export and work with RSVP data. If the transcript's concern was that people were being asked to self-identify through a very real infrastructure, that concern survives and actually gets stronger at this layer of the record.


