Account settings

We have recently implemented Custom Roles in our space that bumped the PO role to Contributor + Custom (eliminating the ability to add new product and granting paid seat access, etc - see attached) We would like the ability to change some of the t...

I would like to have the ability to set an automatic deactivation of user accounts after XX days of inactivity. Use Case: As an admin with a large user base, I frequently have users moving between groups, changing responsibilities, etc. Sometimes...

Aha Score is a standard field in Aha and like many others, you still can configure it based on your business requirements. This is why it would be good that the reviewers' users be able to understand the metrics under that score and have quick vis...

The configuration of work flow statuses is a great tool to customize your view in aha. Unfortunately the Status descriptions are only visible in the configuration mode (which is only available for a specific typ of user). This leads to confusion f...

It would be very useful to be able to set read-only permissions for some fields (either standard or custom fields) based on permissions, or - even better - permission groups. In fact we have some fields on Features and Ideas that should be maintai...

Mistakes do happen, but having a history log helps us determine how big the impact is, and where to begin correcting the issue. It also prevents a case for Aha support.

I would like to have a way to manage my Aha Account in order to disable internal user's ability to generate an API Key?

Paid seat groups are useful for managing the assignment of seats to Roadmaps users. It would be great if this could be extended to support the assignment of Develop seats as well.

Often settings like layouts, terminology, and navigation for parent lines may be purposefully different than workspaces. It would be helpful to drive standards for lines by allowing templates to be applied at those hierarchy levels. A few examples...

We would like to have a core set of common fields used in the field layouts for all products, but there will still be a need to support custom fields needed only by a subset of products. If we could have products inherit a custom field layout and ...