Partner shell
The public portal entry focuses on secure sign-in, localized partner continuity, and a governed access path that can support delivery partners, therapists, resellers, and internal operators.
4
Role types
Partner, therapist, reseller, and admin views are normalized from claims.
3
Review layers
Identity, role review, and admin handling shape the access posture.
1
Access pattern
One sign-in path anchors the protected workspace routes.
What the public portal entry establishes
The entry surface proves that access can be localized, governed, and consistent with the wider ALBAKEYS brand system.
Partner users enter through the same tri-lingual experience as the public site.
Dashboard sections change with normalized role claims after sign-in.
Secure partner entry
The public portal landing page should communicate access posture before a user signs in.
Portal access is framed around configured identity, normalized roles, and a consistent partner-entry surface rather than separate ad-hoc login experiences.
Role requests, partner organization details, and review status are positioned as governable records with visible admin handling.
Partners and operators encounter the same language depth, executive tone, and portfolio framing before they enter protected workspace routes.
Partner access questions
These answers explain what the public portal surface is designed to do.
Resellers, therapist networks, delivery partners, and internal operators who need a protected workspace should use the access-request flow.
The request enters the admin review queue with the requested role, organization context, and the information needed for role and identity handling.
The partner portal is the protected collaborator surface, while the admin console is a separate operational layer for content, intake, access, and publication governance.
Role lens
Requests, documents, and support views for delivery-aligned collaborators.
Role lens
Program-oriented overview with patient-safe context and documentation access.
Role lens
Users, access posture, and shared operational visibility.
Authentication is not configured yet for this environment.