UX - visual summary of approval mechanism
Open
Pay
UX
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
Please explore the suggestion below to devise an approval process for fee changes.
UI features
Every fee change generates a change record
Change record includes:
Before / after values
Reason for change (required comment)
Approval block (status, approver, date)
Fee cannot be re‑activated until the change record is approved
How approval happens
Either:
Manager signs off outside the tool (email / SharePoint / ticket)
Or receives a lightweight review link (read-only view)
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.