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 ...
Guest
about 9 years ago
in Account settings
8
Unlikely to implement
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...
Christina D
over 1 year ago
in Account settings
0
Future consideration
Limit Workspace Permissions for User with Product Line Owner Permission
We need an ability to Limit Workspace Permissions for User with Product Line Owner Permission.
Currently "Users with access to product lines also have access to their underlying products."
Use Case:
We have a number of Product Operations Workspace...
Alex B
about 5 years ago
in Account settings
2
Future consideration
Report on custom fields used in integrations, reports and roadmap views
Today you can identify which layouts and workspaces custom fields are actively used in. However, when looking to manage a large number of custom fields across a large organization, there is no way to determine which integrations are using that cus...
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...
Austin Merritt
over 7 years ago
in Account settings
5
Unlikely to implement
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...
Guest
over 8 years ago
in Account settings
1
Unlikely to implement
Currently we need to delete 1200 users that are inactive. Taking on this endeavor 1 by 1 is timestaking and tedious. Would be great if we could bulk delete. There could be multiple ways to verify this is correct to ensure that no one could uninten...
Shawna Wilson
over 4 years ago
in Account settings
0
Unlikely to implement
Enable Conversion of Product Workspace to Product Line
In the creation / setup phase of workspaces and product lines, we cannot change the workspace designation to a product line. Instead we have to move the data objects from the existing workspace to other workspaces, then delete the workspace that c...
Roger Octobre
over 4 years ago
in Account settings
1
Future consideration
I live in Germany, like to use my apps in US English, want the ISO 8601 date formatting (2017-05-31) and want a space as the thousands separator. It really sucks that there is only a "locale" setting which assumes I want to use a certain formattin...
Guest
almost 8 years ago
in Account settings
5
Future consideration
Automatically fetch the new SSO certificate/fingerprint
When an account is configured to use SSO, occasionally a certificate can be updated/changed in the SSO provider. When this happens, a user trying to log into Aha! will see the error "SAML response certificate does not match fingerprint". The recom...
Emily Yankush
over 2 years ago
in Account settings
1
Future consideration