It would be wonderful if Aha! had the option to customize user permissions when it comes to adding or editing ideas, adding or editing features, etc. For example, one user could have permission to only work with requirements while not having the opportunity to work with features. This idea could be extended to customization opportunity for all aspects of the Aha! platform.
This would be extremely helpful to the product team, as we would like to give access only to the Ideas area for our Support and Services team to help manage Ideas prior to our team moving them forward as a feature.
This is absolutely critical for us. Our customer success team is the first line of engagement around gathering requests, building requirements, and fleshing out Ideas. Our product team then takes these Ideas and promotes to Features as part of the regular roadmapping process. We need to be able to assign specific users (or ideally user groups) to determine what actions they can perform on which objects (Ideas, Features, Epics, etc.) It would be even more valuable if we can configure these types of entitlements down to the field level (what fields can a given user/group read/write/update for a given object, layout, etc.)