As an Aha! admin of product lines, I would like to provide access to the head of strategy to contribute to strategy, but not to also CRUD on releases, epics, etc, so that the person can edit only areas relevant to their role.
Idea: create fine grained permissions for a Head of Strategy role—one that can manage strategy elements but not epics/releases. Perhaps removing the all-or-nothing cascading of permissions could do it.
Thank you for the idea. Given the low volume of support for this idea, we do not have plans to make updates in this area at this time.
Removing the cascading of permissions, or granting the ability to overwrite the inheritance would be extremely beneficial. Colleagues working on strategy in upper hierarchy levels don't necessarily need contributor access to all underlying products.