User management

When our team is commenting back on ideas, we want our customers to know they are employees and their title. We would also like customer to be able to edit their profile and show their title.

Our infosec requires SAML requests to be signed, and don't approve the strict HTTPS certificate checking when sending requests to identity providers. This causes links to our ideas portal to work only if the user is already logged in, which really...

We are allowing all the engineers in our company to view the roadmap information in Aha! by enabling SSO registration. It's a transparency policy that enables the engineers to see how the feature pipeline is determined. Issue here is that SSO crea...

Hello Aha! We have our Ideas portal users vote allocation set at 10. However, we have A LOT of active users who have maxed out their votes. I need a way to do a mass vote allocate increase. For select users maxed out with 10 votes, bump them...

Typically in SSO JIT flows, the metadata about the user, for example First Name and Last Name, are used during User Creation (JIT from SSO), not subsequent User Authentication. For example, if I edit a user in the Admin side, and put in their prop...

As an Aha! Administrator, I would like to be able to manage user permissions by importing a file containing all of my preferences. This would be similar to how I can upload other data types, like features, in order to update various attributes by ...

Based on our organizational structure and roles and responsibilities the "Reviewer" role does not have enough permission and the "Contributor" role has too much. Specifically, we're looking for a role that removes "add manage strategy" from the co...

Currently when deactivating a user, the user then becomes 'greyed' out. This isn't readily obvious due to coloring, resolution, etc. Suggestion is to clearly annotate the user with a Joe Smith - Deactivated or something similar

When my co-workers submit their product gripes on our internal ideas portal, I want it to be internally visible only by default.

This is a very basic, fundamental requirement of any scheduled email distributions for the user themselves as a self serve option... and not an expected admin operation.