Account settings

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 o...

We need the ability to make standard and custom fields mandatory for existing records. When a record is being edited, the UI should flag empty required fields so that the user is prompted to update them. This will help us ensure that critical inf...

It would be useful to be able to customize layouts. For example, add section markers to separate fields for a more organized view, add helper text underneath field names that doesn't disappear as soon as the user starts typing, and arrange related...

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.

What is the challenge? Users who have owner licenses can create workspaces or workspace lines not only under the workspace lines they own, but also other workspace lines they do not own. As admins of the Aha! account, we want to limit user's abi...

What is the challenge? Organizations can have different types of teams leveraging Develop/Teamwork workspaces. With that, they need the ability to define specific standards - workflows, layouts, etc. What is the impact? Admins have to indi...

Some of the user groups in our org need to manage Ideas but we don't want them to view or change roadmaps WIP.

What is the challenge? In Settings > Account > Custom layouts, the primary record types are listed by default and additional layout types are show in a "More" menu. The layout types in the "More" menu do not seem to be grouped in logical w...