Account settings
Sort by:
Trending
Filter by:
Status
Showing 685 of 9641
3
VOTE
Only Allow Users to Create Workspaces under the Workspace Lines They Own
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...
0
Likely to implement
81
VOTE
3
VOTE
Allow admins without a paid license to manage workspace hierarchy
What is the challenge? Some teams have central admins who do not manage work in Aha!, just help configure it for end users. These users have full admin permissions and help administrate the account. This is fine for most settings, but if a customi...
0
Future consideration
4
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
4
VOTE
Option for contributors to be paid seat group owners
What is the challenge? Currently, only billing admins and workspace owners can own paid seat groups. It would be helpful to allow contributors to own paid seat groups as well. This would allow individuals to own the group, without providing them o...
1
Future consideration
43
VOTE
Introduction of further customization user permissions
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...
6
Future consideration
24
VOTE
Apply workspace templates to lines
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...
2
Future consideration
2
VOTE
2
VOTE
Custom tag values should get applied colors as they do with standard tag values
What is the challenge?
Currently when a user adds a new custom tag value, the color defaults to black for the tag, but for standard tags, they get auto-assigned a color
What is the impact?
An admin must go in and manage new tag values if y...
0
Future consideration
1
VOTE
Pause Aha notifications while we perform bulk data imports
What is the challenge?
Some of the data bulk changes we do are tied to portfolio management activities that are not relevant to the Aha users, but the users are getting the notifications for the changes we make.
What is the impact?
Today, ...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved