Account settings

Currently, you can create custom terminology for most of the menu's in Aha and other terminology. I would also like to be able to rename the Roadmap menu (for example to Reports, as this is more meaningful for our company) as the new Roadmap menu ...

One of our Contributors accidentally changed the name of a Workspace. They were unaware that they would have permission to do so, and they did so by mistake. We would like to be able to disallow Contributors from changing (or accidentally deleting...

I'd like to change a custom field from Editable Choice List to Tags. This would let users choose multiple values instead of a single value. But to do this, I have to delete the field and create another one, which destroys the data I've already ent...

Being that we had a situation with deleting workspaces & finding a bug, we realize that 7 days is not enough time to recover data in case the situation isn't uncovered within that time frame. If data is changed (bulk edit, deletion, etc), user...

Who would benefit? Users/organizations that don't follow a standard/defaulted fiscal year What impact would it make? Allowing an organization to set exact perimeters for their fiscal year will allow for accurate reporting. Currently, if one of our...

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

Workspace templates are a great way to encapsulate workspace configurations into a template, so that we can quickly spin up new types of workspaces. However after creating a new template, we have a need to apply that template to a large number of ...

Currently if there are over 500 choices in a custom field, e.g. predefined choice list, the user is forced to use the Manage options area which doesn't allow for easily adding multiple new choices.

We recently had to submit request (692700) because a custom layout that was shared by many workspaces was updated and needed to be reverted back with the fields that were removed because the admin did not know the impact was beyond a single worksp...