/ 02
Three portals,
one fabric.
Foundation Collab is organised around three roles. Each gets the surface it needs and nothing more - but they all share the same tenant data, so what one role sees is consistent with what the others see.
For the parent foundation
Parent portal.
Brand the space, invite partner organisations, set the topics that matter, and watch how the work moves across the network. Activity, announcements, events, documents, member directory, and the wellness arcade.
- White-label brand and palette per tenant
- Member-org roster with map and submissions
- Cross-tenant audit log and capabilities matrix
- Direct messaging into every partner org
For every partner org
Member portal.
A calm home for resources, events, threads, and the people doing the work alongside you. Private wellness center, gratitude wall, mood check-ins, and a tenant-scoped leaderboard for the arcade games.
- Per-org and cross-org messaging (toggleable by the parent)
- Submissions form with version history
- Personal profile with org binding
- Wellness arcade with private mood + gratitude entries
For the platform team
HQ portal.
Quiet rooms behind a locked door. Provision tenants, audit activity across the platform, run health checks, manage moderation queues. The operator surface, deliberately separate from any tenant.
- Platform-wide audit log with actor + tenant filters
- Tenant provisioning + impersonation (with an audit trail)
- Embeddings backfill + moderation surface
- Billing + capability tier overview
/ a note on access
Each portal lives at its own subdomain and is gated by role. A single person can hold multiple roles across portals - a foundation operator might be an HQ admin, a parent admin, and a member of one of the org rosters all at once. The user menu in the top-right corner switches between whichever portals apply.
made with carebuilt for real usedesigned to last.