Account settings
Sort by:
Trending
Status:
Unlikely to implement
Showing 645
20
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...
1
Future consideration
28
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
1
VOTE
Enable merging a many to many relationship custom table field with a predefined tags field
What is the challenge? Currently, it's not possible to merge a many to many relationship custom table field with a predefined tags field What is the impact? Manual effort required to export and import via CSV when creating a new predefined tags fi...
0
Future consideration
6
VOTE
Option for workspace template to not override all settings when first applied
What is the challenge? When applying a workspace template, even if the settings are marked as unlocked in the template, once applied to a workspace the existing workspace settings will still be changed. This is not always the desired experience. I...
1
Future consideration
2
VOTE
User management: filter for date user was created
What is the challenge? To comply with company policy, user accounts created more than 90 days ago, and never used, need to be disabled. What is the impact? Non-compliance with company policy Describe your idea Add a filter to the Settings > Acc...
0
Future consideration
20
VOTE
Allow ability to limit valid values in Feature fields to only display relevant values for the workspace.
When defining features in a workspace, you should only need access to utilize valid values from selected workspaces. Each workspace owner defines and reports on their valid values very differently. When all valid values from every workspace are di...
1
Future consideration
1
VOTE
Disable cloning / copying records
What is the challenge? copied records bring over all data fields - including locked fields and fields used to indicate something was a part of a specific planning period What is the impact? there is no way to identify a record has been cloned, or ...
0
Future consideration
3
VOTE
Ability to edit first and last name of a user
What is the challenge? Ask? . If a transgendered employee who hasn’t had a legal name change yet were faced with this challenge, it would be an afront to the values that our company holds dear. Certainly something we have to address at the point o...
0
Future consideration
12
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 ...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved