Event sponsors and organization access update

The latest Military OS work tightens the link between events, sponsors, and external organization records. Event staff can attach sponsor organizations to a specific event, set the display order, and keep the public logo strip predictable across event pages and ticket surfaces.

The organization record now carries the other half of the workflow. Active association-wide sponsor relationships live on the organization, and those sponsor rows appear automatically on every event. Event-specific sponsors are still managed from the event editor, which keeps one-off sponsorships from becoming permanent organization state by accident.

What changed

The event editor has an event-specific sponsor picker. It lists existing organizations, lets staff select the sponsors for the event, and stores a numeric order so logos render in a deliberate sequence. The public event list, event detail pages, and ticket passes read from the same sponsor data, so sponsor visibility does not need to be rebuilt separately for each surface.

The organization page now separates relationship tracking from access control. Sponsor, exhibitor, corporate partner, and vendor rows describe the business relationship. Organization admin and organization billing admin assignments decide who can operate the external account. That split is the right boundary. A marketing contact can approve logo copy without receiving portal access, and a billing admin can handle invoices without being labeled as the sponsor owner.

Why it matters

Association sponsors are rarely just names on a page. They have logos, websites, fulfillment contacts, billing contacts, event appearances, and sometimes people who need limited access to account details. Treating all of that as one note field would make the product look simpler while making operations worse.

The sharper model is event placement on the event, durable relationship state on the organization, and portal permissions on the person-role assignment. That keeps the admin screens readable and makes sponsor display a repeatable operating workflow instead of a manual publishing chore.

Screenshots reflect the product at the time of writing and may change as Military OS ships updates.

Discussion

Discussion loads here through GitHub-backed comments when JavaScript is available.