Asset Management UI Documentation
Summary
Complete Draft documentation for the verified Asset Management user interface: a single administrative asset tab inside the merged HR Operations workspace, plus read-only employee self-service asset views. The UI reaches the backend through the monolith-shaped compatibility surface, not the native asset-service endpoints.
Audience
Frontend and backend engineers, QA, support, architecture, security reviewers, product owners, and implementation partners.
Overview
The client portal is a React (Vite) single-page application. Asset Management is not a standalone frontend module; it is one module (module="asset") of the shared HrOperationsPage, reached at /hr-operations/assets, plus an employee self-service list at /assets. The admin tab renders a metric strip, an asset form (create/save), a data table with approve, reject, and delete row actions, an approval confirmation modal, and an Excel import control. Employee self-service exposes read-only assigned-asset lists and a simplified request form.
There is no dedicated asset detail route, no dedicated assignment or return screen, no in-UI document manager, and no audit/timeline viewer in the verified frontend. Assignment happens through the form's "Assign To" field, and approval sets status to Issued; return, damage, loss, and retirement are not exposed as dedicated UI actions in the asset tab. These absences are documented, not invented.
The implementation is classified Partial: a functional admin CRUD-and-approval surface and read-only self-service exist, but several backend capabilities (native detail, documents, history, timeline, dedicated lifecycle actions) have no corresponding UI. Frontend role and permission checks control visibility only; the asset compatibility endpoints are tenant-scoped but not role-authorized at the backend.
Documentation map
- UI Overview, Routes and Navigation, Dashboard, and Inventory Workspace
- Asset Form, Requests and Approvals, Employee Self-Service, and Compatibility UI
- Validation and Feedback, Permissions and Visibility, Responsive and Accessibility, UI Testing, and UI Limitations
Requires confirmation
Accessibility conformance, responsive breakpoints beyond verified layout code, and any planned dedicated detail/assignment/return/document/timeline screens require confirmation.
Source References
UI/salary-ui/apps/client-hrms-portal/src/App.tsxUI/salary-ui/apps/client-hrms-portal/src/components/AppLayout.tsxUI/salary-ui/apps/client-hrms-portal/src/pages/hr/HrOperationsPage.tsxUI/salary-ui/apps/client-hrms-portal/src/ess/EssPages.tsx
Related Articles
See Also
Keywords
- Asset UI
- HR Operations workspace
- Employee self-service
Revision Information
- Status: Draft
- Last reviewed: 2026-07-17
- Review cycle: Quarterly