Product only
Only BrainCaps-specific settings belong here.
Keep settings product-scoped, auditable, and privacy-aware.
La route settings doit rester strictement dans le perimetre BrainCaps: options metier, garde-fous de memory, exposition connectorielle, retention et parcours de support. Le shell transverse reste chez PortalHQ.
Tenant-scoped
Retention, export, and deletion must be visible as product responsibilities.
Traceable
Anything crossing into support or operator action needs a visible, auditable path.
What settings can legitimately live here
Only settings that change BrainCaps product behavior for the tenant belong on this route.
- Memory behaviorChoices around retrieval presentation, workspace defaults, or connector visibility.
- Support handoffClear paths to request help when the issue exceeds self-service scope.
- Data lifecycle cuesVisibility into retention, export, or deletion pathways where product ownership applies.
What must stay elsewhere
Several tempting settings categories do not belong in this product surface.
- Membership managementRemains a PortalHQ concern.
- Billing settingsRemain in the shared shell.
- Break-glass or operator controlsRemain private in braincaps360.
What settings should prepare for later hardening
Even the V1 settings route should be compatible with the compliance shape already defined.
- Tenant-scoped retentionFuture settings must not imply shared retention defaults across tenants.
- Export and deletion pathsThe product should make it obvious that these requests exist and are scoped.
- AI governance postureNo hidden training assumptions or silent outbound AI usage behaviors.