Account settings
Sort by:
Trending
Status:
Unlikely to implement
Showing 659
1
VOTE
Display customized terminology on settings screens
What is the challenge? Today customized terminology displays on user facing screens within Aha! but not on settings screens. What is the impact? This makes it hard for users to ensure they are adjusting the right settings for each record type. Des...
0
Future consideration
13
VOTE
Allow to define the scope of tags/choice list custom field values (account vs. workspace)
It should be possible to define whether the values of choice list and tags custom fields (predefined or editable) are shared at account level (current behavior) or limited to workspace level such that workspaces can share a configuration but have ...
1
Future consideration
10
VOTE
Paid Seat group "profiles" for SSO provisioning
As a paid seat group owner, I would like to establish standard permissions for users in my paid seat group that I can apply through SSO at the time of seat provisioning. These permissions include both roles (owner, contributor, custom role) as wel...
0
Future consideration
20
VOTE
Allow ability to limit valid values in Feature fields to only display relevant values for the workspace.
When defining features in a workspace, you should only need access to utilize valid values from selected workspaces. Each workspace owner defines and reports on their valid values very differently. When all valid values from every workspace are di...
1
Future consideration
59
VOTE
32
VOTE
Ability to add PO functions to a Custom Role
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...
8
Future consideration
9
VOTE
Allow Workspace templates to inherit layouts from product line
Who would benefit? Anyone who wants to use a workspace template for things like automation, but wants to use product line inheritance for layout configuration. Our automations are able to improve data quality and reduce administrative overhead for...
1
Future consideration
15
VOTE
Pass data in shared fields between objects through linked objects
We would like data to be passed using shared fields across objects the same way promoted objects work. Today, if a field (e.g UCMGID) exists with same API key in IDeas, Features, Epics etc, that data will be passed when the Idea is promoted. What ...
0
Future consideration
3
VOTE
44
VOTE
As an Admin, I would like the ability to easily see and filter which custom fields are being used by which products and product lines
As a very large account user, we have A LOT of custom fields and we are finding it very hard to manage. Our biggest pain point is that some of our Admins will update a custom field, that they believe is only being used by them in their product, an...
6
Unlikely to implement
© 2025 Aha! Labs Inc.•All rights reserved