RELATED IDEAS
This idea has been merged into another idea. To comment or vote on this idea, please visit APP-I-4162 Ability to add custom fields to the User table.
allow custom fields on user records / have additional information available, like team or business unit
Merged
We are a global company and I would very much like to expand the usage of Aha! to additional business units. At the moment, there is no way I can distinguish which role, team or function a user belongs to. Paid user groups are not really adequate. Not having fields on the user records, is limiting how we can use the system.
If there were additional fields on the user records and we could filter on them, this opens up the possibility of using this information in workflow, automation and on allowing access to workspaces/marketing lines to users from a particular area, rather than having to link users one by one.
1
MERGED
Allow custom fields on User object
I need to be able to add custom fields to the User object so I can identify which Product Segment they work in and what their role/responsibility is in that org. We have six different segments with people of several different roles that have paid ...
2
Future consideration
1
MERGED
Add tags or additional information to users
Need to analyze or group users by various criteria (e.g. region, country, cost center, business unit, etc). Currently, the user list can only be organized by Name, Email, Paid seat group, permissions, Administrator, and Paid Seat. We are currently...
0
Future consideration
2
MERGED
expand the Aha! user record allowing custom fields to be added
Having the ability to add a custom field to the Aha! user record would allow for the ability to report on additional fields at the user level. Being able to pull reporting on those specific attributes on an individual would give a more granular lo...
0
Future consideration
It would be helpful if custom fields would be added to capacity planning. Adding custom fields on users (e.g. manager, division, fulltime/contractor, if time allocations are required and other attributes). And the ability to filter those custom fields in reporting too.
Very important capability to enable use AHA for sharing info with the entire org (Sales, SE, R&D, Technical writers...) Even having even those tags as a fix tags with no edit capabilities can help. It would allow assign the right permissions (R&D - reviewers, Sales = Viewer etc..).
Also important to mention the great sync with LDAP which makes the AHA admin sometimes blind to who is who. If this field could be sync from LDAP - Halleluiah !