Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Account settings

Showing 365

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...
Nicola Rolando about 2 years ago in Account settings 0 Future consideration

Pass data in shared fields between objects through linked objects

We would like data to be passed using shared fields across objects the same way promoted objects work. Today, if a field (e.g UCMGID) exists with same API key in IDeas, Features, Epics etc, that data will be passed when the Idea is promoted. What ...
Karla Johnson about 3 years ago in Account settings 0 Future consideration

Active Directory group integration for user authentication

We would like to give visibility (at least read only access) to Aha to a large amount of users (> 1K) in our organization however this is currently not practical as each user needs to be added manually one by one. Even when using SSO you still ...
Roman Hernandez about 7 years ago in Account settings 1 Future consideration

Amount of changes made by a user when Account Level permissions

What is the challenge? Business Problem to Solve: Utilization report: We would like to know who is utilizing the Aha Account Level? How can we manage the amount of changes made by a user when Account Level permissions have been granted? License co...
Mike Jacobson over 1 year ago in Account settings 1 Future consideration

Follow custom workspace line terminology when viewing Roll up to workspace goals

When a workspace line references its parent, the naming of that parent should match the parent level, not the workspace level. By not reflecting the customized terminology we are introducing layers of confusion for the team members who don’t spend...
Ian Cooper over 3 years ago in Account settings 1 Future consideration

API Key restriction

I would like to have a way to manage my Aha Account in order to disable internal user's ability to generate an API Key?
Mike Jacobson over 4 years ago in Account settings 0 Future consideration

Enable Conversion of Product Workspace to Product Line

In the creation / setup phase of workspaces and product lines, we cannot change the workspace designation to a product line. Instead we have to move the data objects from the existing workspace to other workspaces, then delete the workspace that c...
Roger Octobre about 5 years ago in Account settings 1 Future consideration

Limit Workspace Permissions for User with Product Line Owner Permission

We need an ability to Limit Workspace Permissions for User with Product Line Owner Permission. Currently "Users with access to product lines also have access to their underlying products." Use Case: We have a number of Product Operations Workspace...
Alex B over 5 years ago in Account settings 2 Future consideration

Ability to sort the user grid by AI Credits used

What is the challenge? Now that we have AI credits, I would like to see who is using the credits. The user grid shows how many credits each user has used, but it does not allow for sorting What is the impact? I have to scroll through pages...
Jennifer Lange 21 days ago in Account settings / AI assistant 2 Future consideration

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...
Manny Pannu over 1 year ago in Account settings 2 Future consideration