Account settings
Sort by:
Trending
Status:
Already exists
Showing 657
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
13
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
4
VOTE
Support integration actions within workspace template automations
What is the challenge? Currently, integration actions from automation rules can only be created for workspace-level automations. These automations can only be copied but cannot be applied to a workspace template. Currently, workspace templates are...
0
Future consideration
1
VOTE
Display customized terminology on settings screens
What is the challenge? Today customized terminology displays on user facing screens within Aha! but not on settings screens. What is the impact? This makes it hard for users to ensure they are adjusting the right settings for each record type. Des...
0
Future consideration
7
VOTE
Display a default date format for the entire account
What is the challenge? When screen sharing the roadmap, it's difficult to determine what format dates are in based on locations. What is the impact? It makes it difficult to coordinate dates effectively. Describe your idea Enable us to change date...
2
Future consideration
40
VOTE
Introduction of further customization user permissions
It would be wonderful if Aha! had the option to customize user permissions when it comes to adding or editing ideas, adding or editing features, etc. For example, one user could have permission to only work with requirements while not having the o...
6
Future consideration
50
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
8
VOTE
Hide parking lot from certain user roles
Who would benefit? everyone What impact would it make? limits information leakage and information misuse to parts of the organization who don't need to see in progress epic development before it's put in an official release How should it work? wit...
0
Future consideration
29
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...
1
Future consideration
10
VOTE
Paid Seat group "profiles" for SSO provisioning
As a paid seat group owner, I would like to establish standard permissions for users in my paid seat group that I can apply through SSO at the time of seat provisioning. These permissions include both roles (owner, contributor, custom role) as wel...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved