Account settings
Sort by:
Trending
Filter by:
Status
Showing 644 of 9173
4
VOTE
When updating our Aha! account domain we need embedded links to records in Aha! that reference our old domain to continue to work
We are considering updating our Aha! account domain and would like for links embedded in our Aha! records that reference our old domain to continue to work to provide continuity for our team. Manually updating these links is very time consuming.
2
Planning to implement
20
VOTE
23
VOTE
Custom Fields Permissions
When creating custom fields for ideas or features we need ability to select which user group has rights to edit it. We created a field named owners, with multiple select options from which a product owner can select several names of people that ow...
6
Unlikely to implement
2
VOTE
Allow workspace owner to grant additional permissions when access is given at the line level
What is the challenge? When users have been given access at a line level, workspace owners below that line cannot give them additional access (i.e. if someone is a reviewer at the line level a workspace owner in that line cannot make them a contri...
0
Future consideration
20
VOTE
Ability to select the display order or placement of all the fields for both ideas and features that are displayed in Aha!
Today the idea or feature description is at the bottom of the display and it requires you to scroll down for the description. Can we control the placement of all of the fields which display for Ideas & Features including custom fields and idea...
0
Already exists
14
VOTE
Active Directory group integration for user authentication
We would like to give visibility (at least read only access) to Aha to a large amount of users (> 1K) in our organization however this is currently not practical as each user needs to be added manually one by one. Even when using SSO you still ...
1
Future consideration
8
VOTE
Ability to restrict workspace owners to adding Viewer and Reviewer users only
It would be extremely beneficial to limit the control of adding paid seat user to administrators whilst still allowing workspace owners to add viewers and reviewers to their workspace. Where adding users is required to be restricted to administrat...
0
Future consideration
5
VOTE
Allow for Create SSO access when sharing notes and whiteboards
As a large organization, SSO is required to access authorized tools. When sharing documents (notes/whiteboards) today with a non-Aha! user in my organization, that user would need to start a free Aha! Create account with a UN/PW or Google SSO. We'...
0
Future consideration
6
VOTE
Follow custom terminology in Pivot reports to reflect customized terminology of where the report was originally built, not where the report is run
Pivot table headers use the terminology from the workspace they are being viewed. I want to see the terminology that is used from the workspace line where the pivot table was built. By not reflecting the customized terminology we are effectively i...
1
Future consideration
9
VOTE
© 2025 Aha! Labs Inc.•All rights reserved