ADD A NEW IDEA

Account settings

Showing 627

Allow for Create SSO access when sharing notes and whiteboards

As a large organization, SSO is required to access authorized tools. When sharing documents (notes/whiteboards) today with a non-Aha! user in my organization, that user would need to start a free Aha! Create account with a UN/PW or Google SSO. We'...
Jeanette Resnikoff almost 2 years ago in Account settings / Notes / Whiteboards 0 Future consideration

Record level permission restrictions

What is the challenge? Some features or initiatives are sensitive, so we would like to be able to set record level permission restrictions What is the impact? Anyone who might come across work that isn't being widely publicised in the org Describe...
Nerissa Muijs 6 months ago in Account settings 0 Unlikely to implement

Capacity for teams: API support for team schedules

Ability to create and update schedules via the API. This would allow us to automate team availability (user's PTO or maternity/paternity) and easily update company holidays.
Nathaniel Collum over 4 years ago in Account settings / Capacity planning 0 Future consideration

Bulk edit "custom table relationship" custom fields

Bulk edit is not currently available for "Aha! record relationships" custom fields, nor "custom table relationship" custom fields. Adding the ability, at least for "custom table relationship" custom fields will go a long way to increasing usabili...
Guest almost 6 years ago in Account settings 0 Future consideration

API Access Logs

As an admin, we are addressing logging and monitoring policies in our company. We would like to capture a log of API calls made to a specific Aha instance. We are aware that you have an activity webhook that will notify our system of every change ...
Victoria Morrella almost 4 years ago in Account settings 1 Future consideration

Required fields to be excluded from features in the parking lot

Required fields cannot be excluded from features in the parking lot currently. However, it would make sense that if you have a feature under your parking lot is because you still have to define certain things and you may not count at that time wit...
Guest over 4 years ago in Account settings 0 Future consideration

Allow Reviewers to update existing rows in custom tables

We would like to implement Custom Tables in Releases to collect cross-functional status information from different functional/project teams involved in each release. These teams are not part of product management and would only use Aha! to update ...
Ashton Tsou about 1 year ago in Account settings 0 Future consideration

Make toggling between create/view layouts more obvious within the custom layout editor

The custom layout editor allows you to define the layouts for both the view screen and the create screen for a given record type. The admin needs to toggle between these 2 view types using a drop-down at the top of the screen. This drop-down was n...
Mark Eaves about 3 years ago in Account settings 0 Future consideration

Be able to select a default scenario for all users (Capacity Planning)

Right now, when you add a new scenario (even if it is just a test scenario), all users will be defaulted to that new scenario. We will have dozens of people using the tool, so the inability to get them to all set their own defaults to our standard...
Megan Sanders over 3 years ago in Account settings / Capacity planning 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 6 years ago in Account settings 1 Future consideration