Teams building chat-based approvals (for example Approve/Reject buttons in Slack) need the approval and manual-intervention APIs to act as the person who clicked.

Today, an integration must use a service account or a stored user token, so the service account has to belong to every approver group (a universal approver that bypasses per-user restrictions) and the audit trail records the service account instead of the real approver.

Please support a way for an integration to act on behalf of a user, so Harness checks that user's permissions and approver-group membership and records them as the approver.

For example: an on-behalf-of or impersonation option for service accounts, an OAuth flow where a user authorizes the app once, or tokens limited to approval and manual-intervention actions so storing one does not expose a user's full permissions.