RELATED IDEAS
Merge Ideas Portal Users
Who would benefit? |
Portal Administrators and Community |
What impact would it make? |
This would allow portal admins to ensure users are only able to vote once per idea rather than multiple times by registering more than one email address and/or correct user typing errors during sign-up. |
How should it work? |
A pop-up could appear allowing the admin to pick one account to merge into another. When merging, all ideas would transfer ownership and all unique votes would be reassigned to the to the desired account. |
-
ADMIN RESPONSENov 3, 2025
If your portal users are logging in through SSO, then the SSO provider can pass in a unique ID for that user. Then when they change their email address, it will update their existing user instead of creating a new one. If you need any help with this, you can see these articles for JWT and SAML or reach out to support@aha.io. Hopefully this will be a better solution than manually merging portal users.
7
MERGED
© 2025 Aha! Labs Inc.•All rights reserved
Our customer base frequently experiences consolidations and spin-offs. Over the past five years, we’ve had three different corporate email domains. The ability to merge Ideas portal users would significantly enhance data quality, ensure consistency, and improve customer communication.
We’ve implemented manual processes to address customer email domain changes, but these are time-consuming and prone to errors.
Within the next month, our corporate email domain will change (again!). This will require manually migrating legacy submissions and votes (comments will be lost) for more than 225 internal user accounts tied to the current domain.
We have customers that go through mergers or change company names which leads to sometimes hundreds of users that need to use new email aliases. Today that means approximately 10 minutes per user to identify all of their ideas (both created and voted upon) filling in a csv file with the new data, bulk updating the ideas, then validating the ideas are now assigned to the user. This will only increase as we bring on new customers who eventually change emails. It would be a huge win to be able to simply merge the old user into the new through clicking a button similar to merging an idea or organization.
This would help us tremendously as we store records in our internal system as one person. If a portal account in Aha is using an old email address, we will be unable to match these records. This would help with contact management and user segmentation across different systems. I would love to see a full view of a single person over time. Thank you for your consideration!
Whilst bulk edit allows ideas and associated votes to be moved from one user account to another, the process requires multiple steps across several portals to deactivate redundant accounts. Whilst this is an infrequent activity, the ability to capture everything about a user in a single process and apply this to another record in the event of a domain change, name change or otherwise, would make for a better user experience, ensure a complete record of activity is transferred in one go, and reduce the risk of errors. This would be a useful feature for anyone.