Cross-Tenant Federation

FIPJP, CEP, or any other umbrella tenant authors a survey in the standard builder and, at distribution time, selects cross-tenant federation as the channel. The system enumerates eligible member tenants based on the umbrella's published reach and produces a distribution proposal containing the survey schema, target audience definition (in tenant-neutral terms such as licensed players, club admins, or referees), proposed fielding window, privacy mode, and analytics-sharing terms. Each receiving tenant receives the proposal in its admin inbox and must explicitly accept before any invitation is dispatched on its members; rejection is silent to the originator beyond a status code, and partial acceptance (for example accepting for clubs but not players) is supported through scoped consent.

Once accepted, the receiving tenant takes operational ownership of fielding within its borders: invitations are sent from its branded sender, reminders follow its quiet-hours, channel mix can be adjusted to local norms, and translations are reviewed by its language stewards. Responses are written into the receiving tenant's response store under its privacy mode and never copied across the tenant boundary. Cross-tenant analytics is handled by a federated query layer: when the originator opens the dashboard, queries fan out to each accepted tenant, statistics are computed locally with the same small-cell suppression rules, and only aggregated counts and confidence intervals return to the originator.

The originator sees totals, per-tenant comparisons (where the receiving tenant has authorized that level of detail), and pooled results across all participating nations, but never an individual response. Receiving tenants always retain a full local copy and can run their own deeper analyses, and a complete audit log captures the proposal, acceptance, fielding actions, and every cross-tenant query for regulatory inspection.