Account settings
Sort by:
Trending
Status:
Likely to implement
Showing 686
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
1
VOTE
When configuring a workspace, have to hit update ideas configuration after scorecard selection
What is the challenge?
See the below scenario when configuring a workspace:
Scorecard selection is made
Workflows and other selections are updated
Select update workspace configuration
Scorecard selection goes back to default
Must do t...
0
Future consideration
5
VOTE
Allow custom links within help (?) menu
What is the challenge? For large scale implementations it requires a blend of general Aha! documentation and internally created documentation to provide users with a complete picture. In app we are limited to only Aha! resources What is the impact...
0
Future consideration
51
VOTE
Make admin access multi-level by organization/product line
We have multiple organizations/Business Units/Groups with their own product line in the hierarchy. We would like to be able to make them admin of just that area so that they can make the customizations they need without negatively impacting produc...
7
Future consideration
14
VOTE
Read-only fields based on permissions
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...
0
Future consideration
31
VOTE
Automation rule that adds a new row to a custom table
In my use case we have a custom table on releases to track changes to the release date. I would like to set up an automation rule so that "when the release is updated and the date field changes to anything" then "add a row to the custom table with...
2
Future consideration
2
VOTE
Support multiple billing entities and invoices for the same account
What is the challenge?
Consultants want to have a single Aha! account that they can use for their own work as well as specific client implementations, but they don't want to pay for all of them so they have to create multiple Aha! accounts inste...
3
Future consideration
16
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 ...
2
Future consideration
35
VOTE
Provide the ability to customize what is sent within automation emails
We use automation emails to notify PMs and a few others anytime a new idea is posted. These contain no information beyond the name of the idea and a link. As an Aha admin, I want the ability to select the specific fields I want to include in autom...
8
Future consideration
1
VOTE
© 2025 Aha! Labs Inc.•All rights reserved