Configure Approval Thresholds and Workflow Rules for the Organization
Organization administrators access workflow configuration through the admin settings area. They can set: (1) the mileage threshold below which travel expense claims are auto-approved; (2) the receipt amount threshold that triggers mandatory manual review; (3) whether proxy-submitted registrations always require coordinator approval regardless of value; (4) whether duplicate-flagged registrations are automatically held for review or sent to a separate queue. Configuration changes are versioned and timestamped for audit purposes. The rules are applied by the Activity Approval Service at registration submission time to determine initial status (auto-approved vs pending) and by the queue to determine which warning badges are displayed.
User Story
Acceptance Criteria
- Given an organization administrator navigates to approval workflow settings, when the settings screen loads, then all current threshold values and toggle states are displayed with their last-modified timestamps
- Given the administrator updates the mileage auto-approval threshold, when they save the new value, then the change is persisted with the administrator's identity and timestamp in a versioned configuration record
- Given the threshold configuration is updated, when a new expense registration is submitted after the change, then the Activity Approval Service applies the new threshold to determine whether the registration is auto-approved or placed in the pending queue
- Given the administrator enables 'always require approval for proxy submissions', when a coordinator submits a proxy registration on behalf of a peer mentor, then the registration is placed in pending status regardless of its expense value
- Given a configuration change is saved, when another administrator views the settings, then the updated values and change history are visible for accountability
Business Value
Different member organizations (NHF, HLF, Blindeforbundet) have materially different approval rules mandated by their organizational policies and Bufdir compliance requirements. HLF in particular has strict rules about expense claim combinations and threshold-based attestation. Without configurable approval rules, the system must be hardcoded to one organization's policy, making multi-tenancy impossible. Giving organization administrators direct control over these thresholds also eliminates the need for developer intervention every time a policy changes.
Components
- Activity Approval Service service
- Activity Correction Repository data