The requirement is about recording the exact approval authority for each user and tying that authority to the adjustment. By listing the specific level a user can approve in the user’s record, the system knows who is allowed to act on an adjustment and what steps they can take. When a user requests or approves an adjustment, that assigned approval level travels with the adjustment to determine routing—if further review is needed, the adjustment is sent to the next reviewer who has the appropriate level. This ensures proper authorization, consistent workflow, and an auditable trail of who approved what and at what level. Other terms describe different workflow ideas—grouping levels into buckets, cascading approvals across levels, or a generic notion of a review level—but they don’t name the exact per-user, per-adjustment authority and its routing as precisely as Adjustment Approval Level.