Sponsor support

Sponsor portal routes require a sponsor relationship and should be handled as organization-scoped data. Confirm the requester belongs to the sponsor before discussing leads, attendees, documents, or team membership.

Common requests

1. Ask the sponsor to sign in and open /admin/sponsor; do not request their password.
2. If the page is missing, follow access troubleshooting. Check role and sponsor membership rather than changing unrelated profile data.
3. For lead/meeting questions, verify the sponsor scope and use the portal record. Do not export attendee contact data as a support workaround.
4. For hosted gatherings, use Hosted Invitations. They are private and invitation-only.

Escalate suspected cross-sponsor visibility, unexpected contact disclosure, or a failed permission boundary immediately as a security incident.

Purpose and required role

Use this guide for sponsor-success staff supporting a confirmed sponsor. It covers portal use, not commercial approval, data export, or changing another organization’s access. Sponsor records are organization-scoped; a request from a contact name alone is not enough.

Routes and supported tasks

The sponsor portal is /admin/sponsor; related views include /sponsor/leads, /sponsor/dashboard, /sponsor/success, and /sponsor/intelligence. Source shows portal tabs for Company, Social & Web Links, Marketing Materials, Attendees, meetings when eligible, session when eligible, and Team. Availability can depend on sponsor tier or configuration, so do not promise a tab is enabled until observed.

Support procedure

1. Verify the requester and sponsor relationship through the approved internal process.
2. Ask them to sign in and identify the exact portal route/tab and error. Capture a sanitized screenshot only if needed.
3. For company, links, or materials, guide the sponsor to save through the portal. Confirm the saved state appears; public display needs separate verification.
4. For a missing attendee/meeting/session capability, check eligibility and relationship rather than granting broad access.
5. For team access, use the approved team-access workflow and document who authorized the membership change.

Evidence, side effects, and recovery

A successful save or toast is evidence of the UI action, not an external publication or email delivery. Changes to profile/contact/material data can affect public presentation or sponsor operations; verify intended scope in a clean view. If a wrong value is saved, correct it through the same portal and document the before/after—do not modify database records directly.

Escalate

Escalate cross-sponsor records, unexpected attendee contact data, leads outside the sponsor scope, or a request to bypass roster/eligibility gates as a security incident. See Hosted Invitations for the separate private-gathering rules.