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.
|Release time frame|