Organization
Pending shell context
PortalHQ Deep-Link
Workspace overview for every activated BrainCaps organization.
This is the product entry surface BrainCaps exposes behind PortalHQ. It is where customers land once activation, organization context and entitlements are resolved by the shared shell.
Awaiting Shell Context
Product context resolved server-side from PortalHQ.
PortalHQ has not forwarded an organization context yet. This surface is ready for shell deep-links and becomes tenant-aware as soon as the active organization is propagated.
waiting for PortalHQ
Activation
pending
Plan
Pending entitlement
Billing realm
PortalHQ-owned
No explicit product entitlements resolved yet
Tenant mapping is not exposed on this page yet. Activation reason will appear here when PortalHQ provides it.
Organization context
PortalHQ resolves the organization, activation and billing realm. BrainCaps uses that context to load only the product state that belongs to the active workspace.
Product scope
The client surface focuses on memory, retrieval, connectors, usage and product settings. Cross-product identity and billing stay out of the BrainCaps repository.
Operator boundary
Administrative operations continue to live in the private BrainCaps 360 console. Customer routes exposed here never bounce through the operator backoffice.
PortalHQ remains the shared SaaS shell for identity, billing and organization context. BrainCaps now resolves that shared context server-side on the customer deep-link routes and keeps ownership only of the product surface and business workflows.