ຂ້າມໄປຫາເນື້ອຫາ
ERPStack

ຫ່ວງໂສ້ອຸປະທານ ແລະ ການດຳເນີນງານ

ເອກະສານ

Document management for controlled library, approvals, signatures, search, OCR, templates, retention, and audit evidence.

ນຳໃຊ້ແລ້ວ Evidence-first module page
Primary users
Document controller Approver ຜູ້ເຊັນ Compliance reviewer
/app/documents
App-derived visual
Document control library
Open app route
ການອະນຸມັດ
Reviewer bound
Signatures
Signer bound
ການເກັບຮັກສາ
Hold aware
ພື້ນທີ່ ສະຖານະ ຫຼັກຖານ
ຫ້ອງສະໝຸດ Versioned Record link
ການອະນຸມັດ Queue driven Decision audit
ການເກັບຮັກສາ Lifecycle tracked Hold release proof

ຂັ້ນຕອນຫຼັກ

What the module helps operators complete.

Each workflow is written as an operational path, not a marketing claim, so buyers can understand the day-to-day module fit.

Step 1
Create, version, classify, and link documents to records
Step 2
Submit documents for approval and signature
Step 3
Run OCR/search and manage template-driven documents
Step 4
Apply retention, holds, releases, and audit review

Feature checklist

Capabilities grouped the way operators look for them.

3 capability groups

Document lifecycle

  • ຫ້ອງສະໝຸດ
  • Versions
  • Record links
  • ແມ່ແບບ

Approval and signature

  • Approval queue
  • Signature requests
  • Signer binding
  • Declines

Retention and discovery

  • OCR jobs
  • ຄົ້ນຫາ
  • Retention holds
  • Export runs

Connected module map

How this module exchanges business context with the rest of ERPStack.

Module ຄວາມສຳພັນ
ຄຸນນະພາບ Certificates, inspections, and evidence documents
ໂຄງການ Deliverable and governance evidence
ຄ່າໃຊ້ຈ່າຍ Receipts, waivers, and claim evidence
ປະຕິບັດການຄວາມປອດໄພ Approval, signature, and retention incidents

Governance and reporting

Controls and management visibility expected from a serious ERP module.

ການກຳກັບດູແລ
  • Reviewer and signer binding
  • Retention hold lifecycle
  • OCR and template audit
  • Export checksum evidence
ລາຍງານ
  • Approval status
  • Signature status
  • Retention holds
  • Document audit

AI coverage policy

What ERPStack can honestly claim for this module today.

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 L3 ready
Coverage claim Current AI coverage: Documents L3/L3 ready through the official Agent Tool Registry.
Governance evidence Governance evidence: 3 registered tools, 4 evaluation cases, tenant/RBAC/safe-mode registry controls, and AI log evidence.
Scheduled monitor Scheduled monitor readiness: not in the current proactive-agent monitor wave.
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

Module pages explain value, workflow, control, and proof in one place.

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.

Feature clarity

Buyers can see concrete function groups instead of vague capability claims.

Operational fit

Workflows, users, and connected modules show where the module belongs.

Governance proof

RBAC, audit, SIEM, approvals, and reporting are surfaced as first-class concerns.

Review path

Public pages link back to app routes so reviewers can compare page claims to product surfaces.