Workforce records
- Employee directory
- Departments
- Positions
- Sensitive records
Khong tim thay ket noi internet
Dang thu ket noi lai
Da xay ra loi!
Dang thu ket noi lai
Quy trình nhân sự
Workforce records, leave, attendance, overtime, payroll periods, payslips, approvals, and payment controls.
| Khu vực | Trang thai | Bằng chứng |
|---|---|---|
| Employees | Directory + records | Sensitive change audit |
| Attendance | Correction flow | Approval trail |
| Lương | Payment review | Reconciliation proof |
Quy trình chính
Each workflow is written as an operational path, not a marketing claim, so buyers can understand the day-to-day module fit.
Feature checklist
How this module exchanges business context with the rest of ERPStack.
| Module | Quan hệ |
|---|---|
| Kế toán | Payroll postings and reconciliation evidence |
| Workflow | Leave, attendance, overtime, and payroll approvals |
| Vận hành bảo mật | Sensitive change and unauthorized export visibility |
| BI | Headcount, attendance, payroll, and workforce analytics |
Controls and management visibility expected from a serious ERP module.
AI coverage policy
AI claims are tied to the official Agent Tool Registry, evaluation evidence, safe-mode controls, and scheduled-agent monitor readiness. Roadmap modules only show planned coverage until module-native tools are implemented.
AI coverage ready| Coverage claim | Current AI coverage: HR L3/L3 ready; Payroll L3/L3 ready through the official Agent Tool Registry. |
|---|---|
| Governance evidence | Governance evidence: 15 registered tools, 20 evaluation cases, tenant/RBAC/safe-mode registry controls, and AI log evidence. |
| Scheduled monitor | Scheduled monitor readiness: 1/1 ready (Payroll Payment Approval Monitor). |
| L4/L5 boundary | Remaining L4/L5 gap: no autonomous execution or self-optimizing agent behavior is claimed; write paths remain permissioned, previewed, and confirmable. |
Evidence-first standard
This page structure supports the current public module catalog with app-derived visuals, connected-module evidence, governance proof, and report context that can be compared against real product routes.
Buyers can see concrete function groups instead of vague capability claims.
Workflows, users, and connected modules show where the module belongs.
RBAC, audit, SIEM, approvals, and reporting are surfaced as first-class concerns.
Public pages link back to app routes so reviewers can compare page claims to product surfaces.