Account settings
Sort by:
Trending
Status:
Shipped
Showing 605
7
VOTE
2
VOTE
Add more specificity/granularity around automation logic.
Who would benefit? Both Aha! administrators and the product team members they support through administration of the tool. What impact would it make? It would allow Aha! administrators to automate actions and notifications that advancement can be m...
0
Future consideration
1
VOTE
Full user access panel from the workspace dialot
Who would benefit? Aha admins who need to change user access What impact would it make? When changing access to a workspace (in particular when users have access to a whole line and need to be restricted to only some of the line) it would make it ...
0
Future consideration
7
VOTE
Aha - get Audit history for the custom tables
The data in the master table which has the reference in the Custom Table was modified. when we investigate the history of the custom table, it shows the history of information. But when I look into the audit of the custom id, the history is not sh...
0
Future consideration
2
VOTE
Consider inherited values when copying workspace settings for workspace templates
Who would benefit? Any users creating a workspace template from an existing workspace. What impact would it make? Today if a workspace template is created from an existing workspace, Aha! does not look at inherited settings. For example, at the wo...
0
Future consideration
3
VOTE
More granular sharing security configurations
Today the security configuration forces an account wide setting for sharing views and presentations.This forces us into a situation where we have a once size fits all approach, which is frequently a problem for bigger enterprises.It would be highl...
0
Future consideration
2
VOTE
Develop team owners should be able to manage team members
Who would benefit? Team owners that do not have the customization admin role What impact would it make? Currently Develop team owners do not have a place in the team settings to manage the users in their team, but this is a permission owners have ...
0
Future consideration
20
VOTE
Add more granular admin permission for configuring product lines
In order to maintain consistency across the product hierarchy, it is important to keep control over the naming and organization of product lines and products. In many cases some users should have administrator access to make customizations for the...
5
Future consideration
24
VOTE
Self Registration Capability for User Acess
We are a large organization with many users. We would like to share Aha! with interested individuals and that number could be hundreds or thousands. In order to alleviate that, the recommendation is to allow a self registration process that would ...
8
Future consideration
22
VOTE
Allow scorecards to be inherited from the product line
We have a lot of sub-products in our company, but we'd like to use the same general scorecard, linked to our general product goals, for all of them. It seems that currently scorecards need to be configured for each and every product, which isn't e...
1
Future consideration