Portal workspace
This version is intentionally framed as a clean managed-service portal, not a fake full app. The strongest customer journeys come first, then the backend can connect later.
Submit a managed-service request
The best portal is not just a form. It helps the customer describe the work in the language the service team can act on quickly.
Backend connection
Portal will try to connect to the seeded local backend when available.
Track the active queue
Visibility builds trust. Customers should know what is in triage, what is waiting for approval, what is blocked, and what is complete.
Portal intake requests
Print execution queue
Approvals before release
A managed portal should make approvals clear: what changed, why it changed, what is at risk, and who should sign off before print.
1. Intake and triage
Request is classified as content, template, print execution, or systems issue so the right owner picks it up first.
2. Change review
LabelNex reviews the change against compliance, data mapping, and plant or warehouse execution context.
3. Customer approval
Customer sees the release note, change summary, and impact before confirming the go-ahead.
4. Release and confirmation
Portal records the release state and closes the loop with print execution or support confirmation.
Escalation path when the issue is bigger
Some portal requests are not simple tickets. They reveal deeper compliance, packaging, SAP, or template governance issues and need a stronger response.
Founder review
Use when the issue is urgent, high-risk, or affecting multiple plants, templates, or customers.
Compliance audit
Use when repeated portal requests point to a structural content, process, or release-control problem.
Packaging or SAP engagement
Use when the label issue is really a packaging geometry, data, SAP trigger, or integration problem.
Where portal fits in the platform roadmap
Portal should stay customer-facing and workflow-facing. Studio should handle template work, Admin should handle control and audit, and Backend should unify identity, tenants, jobs, and history.
Portal
Customer requests, approvals, issue tracking, and service communication.
Studio
Template editing, label design workflows, and preview logic.
Admin
Tenants, printers, templates, jobs, audit logs, and role control.
Portal should feel operationally serious from day one.
That means good intake, status visibility, approval clarity, and escalation logic first. Deeper app behavior can come later through `labelnex-backend`, but the customer experience should already build trust now.