Got it, thanks for the response.
I'm not sure if you mean that we could set (1) permissions per job, or (2) if there is a way to set "CAN_MANAGE" for "Jobs" in the workspace generally?
Since this is a CI principal that deploys workflows using the API, it also controls the per Job permissions, so (1) would become a "chicken and egg" type problem where CI would first need permissions to create the job/workflow, but the job is not existing yet so that can't be done. (2) would be exactly what I'm looking for.