Currently there is only one admin role on the BlockBuilderPolicy and FlashtestationRegistry contract, and that is the owner which is a multisignature wallet. It is able to add and remove permissioned workload IDs, as well as upgrade the contract. This means permissioning a new workload ID requires the operationally burdensome process of getting a signature from the multisig wallet owner.
It would be much simpler to have a separate "permissioner" role which would be an EOA hot wallet, or 1-of-N multisig (so that either flashbots or unichain can sign the transaction). That would allow the permissioning process to be automated, and thus much easier/simpler. The owner role would then be in charge of upgrading and adding/removing the permissioner role.