Skip to Main Content
ADD A NEW IDEA

Account settings

Showing 613

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 4 years ago in Account settings 1 Future consideration

Ability to list users who are using API Keys

What is the challenge? Users have generated API Keys to update Aha and the Account Admins would like to know which users are using API Keys. What is the impact? How can we know who is updating using an API and understanding where the API is used t...
Mike Jacobson 5 months ago in Account settings 0 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 10 months ago in Account settings 0 Future consideration

Have workspace templates be default for new workspaces

Who would benefit? anyone who administers an aha account What impact would it make? streamlines work, reduces chance of manual error, reduces need to manually verify items How should it work? allow account admins to set what the default workspace ...
Guest 10 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 10 months 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 almost 6 years ago in Account settings 1 Future consideration

Support logout via SAML

When user logs out of Aha! the logout message should be sent to the IdP. If user logs out of IdP Aha! should process logout message and also logout user. This should be supported for both Aha! and for idea portals.
Chris Waters over 8 years ago in Account settings 2 Unlikely to implement

Custom Fields Permissions

When creating custom fields for ideas or features we need ability to select which user group has rights to edit it. We created a field named owners, with multiple select options from which a product owner can select several names of people that ow...
Guest almost 10 years ago in Account settings 6 Unlikely to implement

Ability to select the display order or placement of all the fields for both ideas and features that are displayed in Aha!

Today the idea or feature description is at the bottom of the display and it requires you to scroll down for the description. Can we control the placement of all of the fields which display for Ideas & Features including custom fields and idea...
Charlene Brennan over 8 years ago in Account settings 0 Already exists

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 11 months ago in Account settings / Development 0 Future consideration