Asset Management Business Overview
Purpose and users
The module provides a tenant-scoped record of inventory and employee-facing asset requests and custody. Employees can submit requests and view assigned items through portal surfaces. Administrative portal users can create records and drive compatible status actions. Exit processes can ask whether unresolved employee-held assets block clearance.
Asset Service owns the aggregate, lifecycle history, document references, audit/timeline evidence, and emitted lifecycle events. Employee identities are references rather than employee master data. Document bytes remain owned by Document Service; notification delivery remains owned by Notification Service; approval orchestration is optionally delegated to Workflow Service.
Boundaries and maturity
Implemented behavior includes registration, list/detail queries, requests, assignment, return, availability, damage, loss, retirement, documents, workflow callbacks, events, clearance checks, evidence, and derived portal metrics. Compatibility routes and a shared HR Operations screen make the module Transitional.
Confirmed exclusions are transfer, reservation, maintenance work records, warranty/service records, vendor/purchase fields, cost/depreciation, locations, theft-specific handling, recovery, disposal approval, procurement, payroll recovery, and finance integration. These are Not implemented, not implied future commitments.
Requires confirmation
Production actors, policy ownership, approval configuration, evidence retention, service levels, and authorization governance require confirmation.
Source References
microservices/src/asset-service/Domain/Asset/Asset.csmicroservices/src/asset-service/Api/AssetEndpoints.csUI/salary-ui/apps/client-hrms-portal/src/pages/hr/HrOperationsPage.tsx