OCM - plan who will need to approve fee changes per product

The audit recommended that all fee changes produce audit records, including approval from someone with the correct authority.

Issue: The audit didn't list specific people per product that would be the approvers.

Goal:
Per product on the platform, create a list of people/roles that can approve fee code changes. (For example, suppose that Entities fee code changes can only be approved by the Registrar.)

Outputs:
1. A spreadsheet or other document that lists the valid approvers
2. A short document explaining how fee change approvals work
3. Training sessions with the approvers at launch, and on an ongoing basis