Skip to Main Content

Account settings

Showing 505

Introduce Customization Owners

As a large organisation with several independent product verticals, we need the ability to lock down account-level customizations (e.g. layouts, custom fields, workflows) by owner (+ collaborators) so that we can retain adequate controls without l...
Joe Buehlmeyer about 2 years ago in Account settings 0 Future consideration

Ability to set a default landing page per workspace

When using a centralized workspace for Ideas, it can be confusing for users to navigate to other pages like the Features board when going to the Ideas workspace from another workspace. In some cases users are taken to sections of the navigation th...
Stephanie Lechner 10 months ago in Account settings 0 Future consideration

Report on custom fields used in integrations, reports and roadmap views

Today you can identify which layouts and workspaces custom fields are actively used in. However, when looking to manage a large number of custom fields across a large organization, there is no way to determine which integrations are using that cus...
Jeanette Resnikoff 10 months ago in Account settings / Reports 0 Future consideration

Dynamically adjust whitespace on "Workspaces" page in Settings

Who would benefit? Customers with a lot of workspaces and workspace lines What impact would it make? This would make it easier to see more content on this page at once and more easily adjust the hierarchy and edit workspaces. How should it work? T...
Maria Plotkina 5 months ago in Account settings 0 Future consideration

Allow renaming of Parking Lot

Add "Parking Lot" to the terminology area and allow a user to rename this. We have always used "Backlog" as our holding area for unscheduled ideas. When exporting the data to a report, executives aren't quite sure what "Parking Lot" refers to!
Guest almost 7 years ago in Account settings 6 Future consideration

Add more specificity/granularity around automation logic.

Who would benefit? Both Aha! administrators and the product team members they support through administration of the tool. What impact would it make? It would allow Aha! administrators to automate actions and notifications that advancement can be m...
Christina D 5 months ago in Account settings 0 Future consideration

Consider inherited values when copying workspace settings for workspace templates

Who would benefit? Any users creating a workspace template from an existing workspace. What impact would it make? Today if a workspace template is created from an existing workspace, Aha! does not look at inherited settings. For example, at the wo...
Kristina Gass 5 months ago in Account settings 0 Future consideration

Custom Field - Internal Name & Choice Lists Report Display

When creating reports with custom fields, there can be many fields within an account that have similar names that will display as field options. We use the internal name to help differentiate and allow the user to select the right field they are l...
Karla Johnson over 1 year ago in Account settings 0 Planning to implement

Allow the selection of epic timelines as default view for Roadmaps > Features

Who would benefit? What impact would it make? How should it work? Allow the additional selection of epic timelines if epics are enabled for the workspace.
Chris Zempel 3 months ago in Account settings 0 Future consideration

Develop team owners should be able to manage team members

Who would benefit? Team owners that do not have the customization admin role What impact would it make? Currently Develop team owners do not have a place in the team settings to manage the users in their team, but this is a permission owners have ...
Jason Gillmore 6 months ago in Account settings 0 Future consideration