Dragon Guard WMS Web is the browser-based administrative frontend for the Dragon Guard Warehouse Management System, built by Grupo MAS on Angular 15 and PrimeNG 15. It provides warehouse administrators and supervisors with a structured interface for creating and managing operational documents, configuring multi-tenant settings, and monitoring inventory — while physical execution (receiving, posting, and scanning) is carried out exclusively by the companion MAUI handheld application.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/CodexaCP/DG_WEB/llms.txt
Use this file to discover all available pages before exploring further.
What is Dragon Guard WMS Web?
Dragon Guard WMS Web is the Angular 15 + PrimeNG 15 administrative frontend in the Dragon Guard WMS ecosystem. Its sole mandate is document administration: creating receipts, shipment orders, inventory adjustments, and multi-tenant configuration. It never performs physical warehouse operations — those belong to the MAUI handheld app.The Three-Layer Ecosystem
The Dragon Guard WMS platform is composed of three cooperating layers:| Layer | Technology | Responsibility |
|---|---|---|
| Web Frontend | Angular 15 + PrimeNG 15 | Document creation, admin configuration, inventory management |
| Backend API | .NET (Wms.Api) | Business logic, persistence, authentication, tenant management |
| Handheld App | .NET MAUI | Physical receiving, posting, barcode scanning on the warehouse floor |
Role, Guard, and Route Mapping
Access to the Angular application is controlled by three route guards, each protecting a distinct section of the dashboard:| Role | Guard | Protected Route |
|---|---|---|
| Authenticated user | authGuard | /dashboard/** |
| ADMIN | adminGuard | /dashboard/admin/** |
| SUPERADMIN_SUPREMO | supremeGuard | /dashboard/supreme/** |
- Standard authenticated users land on
/dashboardafter login. - Users with the
SUPERADMIN_SUPREMOrole are redirected to/dashboard/supreme, which exposes cross-tenant management capabilities not available to regular admins.
Core Services
Two services form the backbone of every feature module:WmsService — Located at src/app/layout/service/wms.service.ts, this is the central API client. All HTTP communication with the Wms.Api backend is funneled through this service. Feature components inject WmsService rather than making direct HttpClient calls.
AuthService — Located at src/app/core/service/auth.service.ts, this service handles authentication, token storage, and session state. The JWT token is always stored in sessionStorage — never in localStorage. This ensures the session is automatically cleared when the browser tab is closed, reducing the risk of credential leakage on shared workstations common in warehouse environments.
Explore the Documentation
Quickstart
Install dependencies, configure the backend URL, and run Dragon Guard WMS Web locally in four steps.
Architecture Overview
Deep-dive into the three-layer ecosystem, module structure, and data flow between web, API, and handheld.
Auth & Session
Understand how AuthService, route guards, and sessionStorage-based token management work together.
API Reference
Browse the Wms.Api endpoint reference, starting with authentication and session management.