Dragon Guard WMS Web maintains a comprehensive audit trail of all data changes across the system, regardless of where they originated. Whether a record was modified through the web application, the handheld scanner interface, the REST API, or an internal system process, the change is captured and made available for review. The audit module exposes this trail through two distinct screens — one scoped to a single tenant, the other offering a cross-tenant global view for supreme administrators — so that operations teams, directors, and platform administrators can quickly investigate what changed, who changed it, when, and from which entry point.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.
Two Audit Surfaces
Dragon Guard provides separate routes for tenant-level and platform-level audit access:- Tenant Audit
- Supreme Audit
Route:
/dashboard/admin/auditThe tenant audit screen is the standard operational log for day-to-day review within a single company. It displays every recorded change that belongs to the authenticated user’s tenant.Accessible roles:ADMINSUPERVISORDIRECTORGENERALGENERAL_SUPERVISOR
WmsService sends the companyId with every request, and the backend re-resolves the tenant context independently on each call. Tenant users cannot see records from other tenants regardless of what parameters they supply.API Endpoints
Both audit screens are backed by the same two endpoints:| Method | Endpoint | Purpose |
|---|---|---|
GET | /api/audit/logs | Retrieve audit log entries (filtered by role scope) |
GET | /api/audit/tables | Retrieve the list of auditable table names for filter dropdowns |
/api/audit/logs. Tenant-role requests automatically receive only their own tenant’s data; supreme requests can receive data across all tenants.
Filtering Capabilities
- Tenant Filters
- Supreme Filters
Tenant users can narrow the audit log by:
| Filter | Description |
|---|---|
| Table | The database table or entity that was modified (populated from /api/audit/tables) |
| Action | The type of operation: CREATE, UPDATE, or DELETE |
| Actor | The user who performed the change |
| Origin | The entry point: Web, Handheld, API, or System |
| Free text | Keyword search across log fields |
Change Detail View
Each audit log entry exposes the full JSON payload of the change — the before state, the after state, or both, depending on the operation type. This detail is rendered in the web UI as formatted JSON so that reviewers can inspect exact field-level changes without needing direct database access.Operations that originated from a handheld scanner device are fully visible in the web audit UI. The
origin field identifies the entry point as Handheld, and the JSON detail contains the same level of field-level change information as a web-originated change.- Verifying that a specific field was changed to the expected value
- Identifying the precise timestamp of a change for dispute resolution
- Reviewing automated system changes (origin: System) for debugging
Sidebar Menu Placement
The audit screens appear in the Dragon Guard navigation sidebar based on the authenticated user’s role:Tenant Users
Users with any of the permitted tenant roles see an Auditoría section in the admin sidebar containing a Bitácora entry that links to the tenant audit screen.
Supreme Users
SUPERADMIN_SUPREMO users see a Bitácora entry inside the SaaS block of the supreme sidebar, linking to the global audit view.