Account settings
Sort by:
Trending
Status:
Future consideration
Showing 649
1
VOTE
View more than 20 users at a time from account settings
Configure a drop-down selector to allow an administrator to view more than 20 users at a time, for example (20, 50, 100, 500, 1000). Currently, if you try to check a few users for a bulk update and then navigate to the next page of users, the chec...
0
Future consideration
1
VOTE
Add ability to view more than 20 users at a time from Account Settings
Adding the ability to view more than 20 users at once, preferably through a drop-down selector (20,50,100,500,1000) would make bulk edits of user permissions easier for administrators. Currently if you select a user and then navigate to the next p...
0
Future consideration
1
VOTE
Allow deletion of types and other data while still in use
There are several places in Aha! where we disallow a user action because an object is in use. For example, users can't delete a custom type while records are using it. We already have an elegant solution in place for this when changing from one wo...
0
Future consideration
3
VOTE
4
VOTE
Extend product tree to support different configurations of a product line
I manage a product line where each product has different configurations. Currently I get around it by making different releases, but it really doesn't solve the problem because the different configurations have different requirements. So, being ab...
1
Unlikely to implement
4
VOTE
4
VOTE
In workflows, add the ability to limit setting a certain status to certain users.
In workflows, most of the time a status like "approved" is available. However, at the moment everybody can set this status, so it pretty useless.
If only certain users (e.g. with a certain role) could set the status to approved it suddenly gets v...
2
Unlikely to implement
3
VOTE
Provide product managers with secondary way to manage reviewer and viewer access by product
Today, administrators have to manage all aspects of access control for users to access product records for the business units in order to maintain the unit's structure/implementation of Aha! This is not scalable for the 5 admins in our unit. Produ...
0
Already exists
2
VOTE
Ability to undo changes in the Activities log
When I make a change in Aha! said change is shown in the activities log. The user should have the ability to revert the change made from within the activity log. This functionality should be such that a single change, multiple changes, or date ran...
2
Future consideration
3
VOTE
Clarify the use of the term "allocate seat", as it's not clear a seat can be unpaid. :-)
Hi, I had a human-error issue where I had two users in my user list that I couldn't figure out how to give them view access. I clicked the viewer access button, but nothing would happen. It turns out it was because I wasn't clicking "allocate seat...
0
Will not implement
© 2025 Aha! Labs Inc.•All rights reserved