ADD A NEW IDEA

FILTER BY CATEGORY

Account settings

Showing 467

Ability to require Paid Seat Group selection

We have Paid Seat Groups established, and have an internal policy that all licensed users need to belong to a seat group. However, we still have admins who forget to add this because they aren't promoted for it when adding a user from products>...
Guest almost 5 years ago in Account settings 2 Unlikely to implement

Use Gravatar for user avatars

Simple one, use Gravatar instead of default image for your users if they haven't added a profile pic. https://en.gravatar.com/site/implement/images/
Guest about 9 years ago in Account settings 2 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 1 year ago in Account settings 0 Future consideration

Default Landing Page

As an organization we'd like to ensure we navigate all Aha users to a specific landing page when logging in. We'd like to set this to the features list view but it could change and so we want to make it customizable across all users. Two important...
Guest over 4 years ago in Account settings 4 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 5 years ago in Account settings 1 Future consideration

MS365 SSO feature

Hi, Adding the identity provider based on ms365 server could be a great idea.
Guest over 1 year ago in Account settings 0 Future consideration

Apply workspace templates to lines

Often settings like layouts, terminology, and navigation for parent lines may be purposefully different than workspaces. It would be helpful to drive standards for lines by allowing templates to be applied at those hierarchy levels. A few examples...
Jeanette Resnikoff over 1 year ago in Account settings 0 Future consideration

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 over 1 year ago in Account settings 0 Future consideration

Allow access to Mockup tool for users with reviewer security

Mockup provides a powerful method for idea contributors to communicate their ideas. However the mockup tool is only available to users with contributor or greater permission. But contributor is too permissive, allowing user to create features, str...
Guest over 5 years ago in Account settings 0 Future consideration

Preserve history when converting from one object type to another

Currently when an object is converted to another object type from within Aha! the history is cleared on the new object (Initiative to Master Feature, for example) From an audit and logging perspective it would be preferable if the history was pres...
Justin Woods over 5 years ago in Account settings 1 Future consideration