Account settings

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...

What is the challenge? The ability to rename a Tag with the same name as an existing tag is a bug, which needs to be fixed. What is the impact? It allows creation of multiple duplicate tags which leads to inconsistencies and confusion with...

When an account is configured to use SSO, occasionally a certificate can be updated/changed in the SSO provider. When this happens, a user trying to log into Aha! will see the error "SAML response certificate does not match fingerprint". The recom...

Who would benefit? Customers who are required to share feature documentation with enterprise or large government clients What impact would it make? Ease of hiding internal information or displaying only customer relevant information How should it ...

I live in Germany, like to use my apps in US English, want the ISO 8601 date formatting (2017-05-31) and want a space as the thousands separator. It really sucks that there is only a "locale" setting which assumes I want to use a certain formattin...

What is the challenge? Difficult to implement continuous user monitoring processes without knowing user activity What is the impact? Privacy risk Describe your idea Add last login / activity date/timestamp to Users module

What is the challenge? Making billing changes in advance of subscription renewal requires communicating with Aha! support What is the impact? Since information is not even visible in the user interface, it's confusing. Because the details aren't k...

Who would benefit? All users What impact would it make? owner can customize the homepage they would like to highlight for team members. (for example: quick start guide note) How should it work? Owner can set default homepage for each workspace.

What is the challenge? It is possible to update a user's current paid seat group via a CSV import by adding a column for that field and inputting their new group info, but there is no way to fully remove a user from a paid seat group via this meth...

We have a large set of custom fields and the fields evolve over time. This means fields are withdrawn from use periodically, but there's no way to mark a custom field as archived and so prevent it from being available to include in a layout or rep...