student
Student path
For students entering cohorts through university-linked programs, labs, or course-connected work.
Continue in BEAM HomeJoin Forge
Forge routes participant registration through BEAM Home.
No separate Forge auth system is created here. These links pre-tag the handoff with `organizationId = org_beam_forge`, `cohortId = cohort_beam_forge_launch`, and `entryChannel = forge.beamthinktank.space`, following the BEAM Home handoff pattern.
Existing BEAM Home code persists sign-in and handoff data in Firebase client auth plus profile documents. Forge reads those documents back for the member view.
community
Community path
For local participants, independent builders, and public-facing collaborators joining Forge delivery or R&D.
Continue in BEAM Homebusiness
Business / partner path
For partner organizations, sponsors, client contacts, and operator-side collaborators entering the ecosystem.
Continue in BEAM HomeWhat BEAM Home currently provides
Participant identity model: organizations, cohorts, participant profiles, organization memberships, cohort memberships, and source attribution.
Public role feed: `GET /api/roles` backed by the Readyaimgo BEAM roles feed.
Work-context lookup: `GET /api/participant/work-contexts` using handoff fields such as `sourceDocumentId`, `sourceStoryId`, and organization metadata.
Handoff persistence: BEAM Home stores the payload at `users/<uid>/profiles/beamHandoff` and onboarding/profile data under sibling docs.