My ideas: Account settings
Sort by:
Trending
Status:
Likely to implement
Showing 667
42
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
5
VOTE
PHI Deletion - Personal History
What is the challenge? is is crucial for maintaining patient privacy and complying with regulations like the Health Insurance Portability and Accountability Act (HIPAA) in the United States. What is the impact? Compliance and Legal Describe your i...
0
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
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
1
VOTE
Restrict visibility on initiative or feature based on their status
What is the challenge? The content of certain initiatives or functionalities must be shared with stakeholders for validation. However, we do not want these stakeholders to have access to all initiatives and features that are not yet in Validation ...
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
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
14
VOTE
Allow to define the scope of tags/choice list custom field values (account vs. workspace)
It should be possible to define whether the values of choice list and tags custom fields (predefined or editable) are shared at account level (current behavior) or limited to workspace level such that workspaces can share a configuration but have ...
1
Future consideration
1
VOTE
add the ability to set workspace template to 'draft' status
What is the challenge? Workspace owner can apply the workspace template that is not ready to MTP What is the impact? Hard to manage workspace template that still in draft stage Describe your idea ability to hide workspace template in workspace cre...
0
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