The Gap: When a user approves or submits a Feature Flag change request via the API using a personal API token, the "Approver" or "Submitter" field in the Harness UI displays the Token Name (e.g., "Agent") rather than the User Email.

The Impact: This breaks the audit trail. Security and compliance teams cannot easily verify who authorized a change without cross-referencing token IDs or relying on manual comments, which is prone to human error.

The Ask: Ensure that API-driven actions performed with personal tokens surface the associated user's identity (Email/Name) in the UI, matching the behavior of manual UI actions.