Project Template Setups

 We have an SOD requirement where we don't want project costing users to have access to project setup menus nor do we want users with access to project setup menus to have access to project menus.  The problem we encounter is that neither user ends up having access to modify project templates.  We end up giving temporary access to the seeded responsibilities that can access both functionality.  This results in additional administrative burden.  

Has anyone else encountered this issue or have an idea of how to address it?

-Nathan