Workflows · inbox · step history · RBAC
One approval engine for every operational sign-off
Define workflows once in Settings — then purchase requests, leave, travel, grants, hiring, and e-signature changes route through the same inbox with step history approvers and auditors can replay.
Approval definitions
Configure steps and approver roles in Settings — aligned to your delegation matrix, not hard-coded.
Unified inbox
One place for PRs, leave, travel, grants, hiring, and e-signature changes.
Audit-ready history
Each instance records steps, actors, timestamps, and approve or reject reasons.
Governance without a separate approval tool
One engine powers sign-off across modules — data-driven per tenant so country offices share patterns, not duplicate spreadsheets.
Tenant workflows
Administrators map approval definitions to document types and value bands in Settings.
Cross-module inbox
Approvers act on pending items from one inbox — including e-signature change requests.
Instance detail
UUID deep links open full step history for notifications and audit response.
RBAC enforcement
Catalog privileges gate who may approve — UI hiding is never the only control.
Configure once, reuse everywhere
Enable the approvals module and wire definitions before operational modules route documents.
- Inactive definitions stay out of pickers for new documents
- Step serializers for web inbox and API consumers
- Rejected items return with reasons to the submitter
-
1
Enable approvals
Toggle `approvals` for the tenant. Ensure functional roles exist for approver groups.
-
2
Define workflows
In Settings → Approvals, create definitions per document type with ordered steps and roles.
-
3
Operational modules route
PR, leave, travel, grants, and hiring submissions pick the matching definition automatically.
Speed with control
Field staff submit once; approvers act from inbox or links; approved items unlock the next step where configured.
Document submitted
A purchase request, leave form, or travel clearance creates an approval instance.
Steps route by policy
Each step assigns the next role — manager, HR, finance, or programme lead.
Approved or returned
Full history remains for donors and auditors; rejections explain what to fix.
Powers sign-off across
Approvals is the shared engine behind these modules.
Frequently asked questions
Common questions from NGO programme, finance, and IT teams evaluating this module.
Which documents use the approval engine?
Purchase requests and orders, leave and travel, grants, hiring, bank changes, and e-signature replacements can all use tenant-defined workflows.
Is there one inbox for approvers?
Yes. The approvals inbox lists pending items across document types with step history for audit response.
Who configures approval steps?
Organisation administrators define approval definitions in Settings aligned to delegation of authority.