Account settings
Sort by:
Trending
Status:
Future consideration
Showing 644
1
VOTE
Integration of company's proprietary AI engine with Aha!
What is the challenge? User can only use default AI engine. Due to company's cybersecurity polices, we cannot enable AI related features. What is the impact? By integrating company own AI engine, the system will benefit from enhanced data security...
0
Future consideration
7
VOTE
After provisioning a new user via SSO, go to their pasted URL instead of the homepage
What is the challenge? An Aha! user shares an internal link to an Aha! report. Someone in the company without an Aha! account clicks on that link. They are automatically provisioned an account via SSO and has view access to all workspaces. Instead...
0
Planning to implement
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
2
VOTE
Support worksheet custom fields in automated scorecard metrics when an idea is promoted
What is the challenge? I have a worksheet that is used on multiple record types. I want to use that worksheet in an automated metric in a scorecard that is shared across those record types. This is not possible today. When you select multiple reco...
0
Future consideration
2
VOTE
Surface error details when importing users via CSV
What is the challenge? If certain entries in a user import CSV are invalid, Aha! does not process those as part of the import and shows an "Alert" with the failures. It does not identify which line(s) or record(s) in the CSV have the error. What i...
0
Future consideration
19
VOTE
Ability to configure scope of selection for custom "users field"
What is the challenge? Based on our use case, we need the ability to configure the scope of selection for the custom "users field" What is the impact? Not able to configure the scope of selection. Describe your idea Need ability to configure the s...
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
13
VOTE
Sort the list of release templates to appear in alphabetical order or set manually
What is the challenge? Large lists of release templates can be difficult to manage and sort. Not having a set list and being able to sort the order alphabetically or manually increases the time it takes to find a release template. This is also the...
0
Future consideration
11
VOTE
Delivery Risks - Ability to Inherent to Child Workspace
What is the challenge? If one product line (parent workspace) wants to implement Delivery Risks, we would need to individually go through the settings on each child workspace to configure. What is the impact? It is very time consuming for large pr...
2
Future consideration
55
VOTE
User permissions: prevent users from deleting records
We occasionally have situations where data is deleted and then we realize it needs to be recovered. If we notice this within 7 days we can restore the records from the recycle bin, but we would prefer to disable the ability to delete records for s...
3
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved