Currently, the Direct Referral Expiration Threshold can only be configured globally within System Referral Settings. This forces a single, system-wide timeline across all programs.

Business Impact:
Operational needs vary significantly by program. For example, Program A may require a strict 7-day expiration threshold, whereas Program B needs 30 days. The current system only allows for one universal setting, forcing communities to adopt thresholds that are either too strict or too lax for their various programs.

Proposed Solution:
Allow System Administrators to configure the Direct Referral Expiration Threshold at the individual program level (while retaining the system default). This gives admins the ability to tailor settings to meet each program's unique requirements for direct referral expirations.