Our company works with sensitive data and we would like to globally shut off the ability to add attachments. In order to meet security requirements, we have quarterly auditing of attachments in addition to coaching users to insert an SSO protected...
Cindy Datlof
about 5 years ago
in Account settings
0
Future consideration
Extend product tree to support different configurations of a product line
I manage a product line where each product has different configurations. Currently I get around it by making different releases, but it really doesn't solve the problem because the different configurations have different requirements. So, being ab...
David Spada
about 10 years ago
in Account settings
1
Unlikely to implement
Support PKCE based Auth Code requests for OIDC SSO portals
We request that Aha! enhance their security posture as it relates to authentication and follow industry recommendations: https://oauth.net/2/pkce/ “PKCE is not a replacement for a client secret, and PKCE is recommended even if a client is using a ...
Joe Granville
over 2 years ago
in Account settings
0
Future consideration
In workflows, add the ability to limit setting a certain status to certain users.
In workflows, most of the time a status like "approved" is available. However, at the moment everybody can set this status, so it pretty useless.
If only certain users (e.g. with a certain role) could set the status to approved it suddenly gets v...
Guest
about 10 years ago
in Account settings
2
Unlikely to implement
We have over 250+ custom fields being utilized by various workspaces. Because we cannot assign a custom field to a particular workspace all 250+ fields are visible in every filter in every workspace. If we could have the ability to define which wo...
Jake Ludwinski
about 5 years ago
in Account settings
4
Future consideration
Within Marketing, Business and Project Lines, the customize terminology setting is broken and creates an inconsistent user experience that confuses users. Within the 'Customize Terminology' setting (Settings > Product Line > Terminology), if...
Carl Ambrus
about 5 years ago
in Account settings
0
Future consideration
Line and Workspace management - stop collapsing the Line / Workspace hierarchy each time you complete a Line
If we leverage UX / UI, when a user-persona leaves a data structure in a window, they should expect it to remain the way they left it when they return, or complete a task Currently, when I go to the Customized Workspaces --> then expand some or...
Guest
about 5 years ago
in Account settings
0
Future consideration
Opening 2-factor authentication to other providers
aha!'s 2-factor authentication implies signing up with a designated 3rd party. We would like to include aha! with the other solutions in our IT portfolio, for which 2-factor authentication is supported by a different supplier than aha!'s partner.
Guest
about 5 years ago
in Account settings
1
Future consideration