BrightLabs ERP Cloud
Self-service ERPNext tenant onboarding for customers, with a separate BrightLabs operations workspace for review, approvals, support, and evidence.
Status summary
Entry paths are separated before authentication.
Public access
Unauthenticated
Customer path
Create Account
Staff path
Login
Portal entry paths
Clear entry points keep customer identity, staff identity, and operations evidence separated from the first screen.
Customer ERPNext accessTrial and paid journeys stay on the customer path.
Customer
BrightLabs staff accessCorporate Entra sign-in stays separate from customer login.
Staff
DEV launch readinessEvidence and operations stay approval-gated.
Guarded
How access starts
The landing page explains the two approved entry paths without exposing authenticated workspace data.Create Account
New customer accounts start with the customer External ID path, then continue through profile, plan, approval, provisioning, and tenant access.
Customer-only
Login
Existing customers and BrightLabs staff use Login, then choose the correct identity lane on the sign-in page.
Chooser
BrightLabs workspace
Staff operations, approvals, and support access stay inside the corporate Entra-backed admin workspace.
Staff-only
Launch-readiness guardrails
What this page can do
PBI 090 is a portal UX pass. It does not create tenants, approve payments, seed ERPNext roles, deploy infrastructure, or change identity provider configuration.
Login/sign-in
Create Account/sign-up
Staff accessCorporate Entra chooser
Customer accessExternal ID chooser
Boundary
The customer and staff workspaces remain separated by their existing auth routes and session cookies.
Customer cookiebl_customer_session
Staff cookiebl_staff_session
Customer routes/customer/*
Staff routes/admin/*