Problem Description: The partner-engineering group is used on c.rh.c (insights mode) but not PAH (standalone mode) and therefore does not have its permissions tracked in migrations. In insights mode we don’t have user management, so any permission edits are done manually. Also for ephemeral environments using insights mode, there is no partner-engineering group to assign a user in order to do partner-engineering testing, and it must be done manually each time.

Proposed Solution: Add a post deploy script to manage the partner-engineering group permissions that can be used for c.rh.c and ephemeral env. Use the permissions documented here