Account settings
Sort by:
Trending
Status:
Showing 653
67
VOTE
Indicate required fields when editing a record
We need the ability to make standard and custom fields mandatory for existing records.
When a record is being edited, the UI should flag empty required fields so that the user is prompted to update them. This will help us ensure that critical inf...
13
Future consideration
1
VOTE
Name of workspace when granting access is too long
What is the challenge? When granting access, the workspace name is only about 2 inches across then it is "..." if the workspace name is longer than this. What is the impact? Hard to navigate and requires exiting the interface and reviewing in the ...
0
Likely to implement
1
VOTE
User Access Provisioning - When reactivating and adding access at the same time
What is the challenge? When reactivating a disabled user account, there is not a way to enable the account and assign permissions simultaneously. I first need to enable the user account, then re-open the modal and assign access as a second step. W...
0
Likely to implement
92
VOTE
Allow sorting records in custom tables
Custom table records are currently sorted by order of creation. Since users often create more important/common records first, the important ones end up at the bottom of the list. Instead, allow sorting these records via drag-and-drop (or at least ...
14
Future consideration
10
VOTE
Allow immediate delete for brand new workspaces
Currently workspaces can only be archived. They cannot be instantly deleted. This is a great safeguard to prevent real workspaces from actually being deleted. However it causes problems when you accidentally create a workspace as a line, or vice v...
0
Future consideration
76
VOTE
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
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
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
© 2025 Aha! Labs Inc.•All rights reserved