Account settings

What is the challenge? Aha! currently supports Duo for two-factor authentication (2FA). However, many organizations standardize on other MFA providers such as Microsoft Authenticator, Okta Verify, or Google Authenticator. Relying solely on Duo c...

What is the challenge? Deleting the Archived workspaces today is a manual process. This becomes a time consuming process if there are thousands of workspaces to be deleted. It would be great if Aha! provided an account level configuration setti...

What is the challenge? Right now, if you want to reuse a workspace prefix, you have to follow many steps including deleting all previous records with the prefix assigned. This can prove challenging with parking lot releases that cannot be delete...

What is the challenge? We release at the epic level, not the initiative level. We are struggling to prevent team members from promoting ideas to the initiative level, when they do the ideas get lost and/or there's no clear determining factor on if...

What is the challenge? The banner if permanently on the screen takes up a TON of real estate What is the impact? Cannot see full screen to work on with static messages Describe your idea Optimize the banner to pivot to the size of the text better

What is the challenge? Archived workspaces can only be deleted one workspace at a time. When you have potentially hundreds of archived workspaces this can be time-consuming. What is the impact? Long time to delete archived workspaces D...

What is the challenge? Users often delete work items that had active or completed work associated with them. Even if the work has been cancelled or abandoned, we do not want the record of the work that was completed to be deleted from the system. ...

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...

What is the challenge? Currently, AI credit limits in Aha! are enforced at the individual user level. For organizations managing large numbers of users, especially across multiple teams, this creates administrative overhead. Administrators must ...

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...