The new proxy voting is something that our sales/services teams have asked for but not something that we can implement at this time. It seems that when turning the feature on any users with access to the private portal (for us this is all of our customers) would be able to proxy vote.
I would only ever want our employee/partner email users to be able to use the proxy vote feature before this feature become usable.
Unfortunately we are unable to take advantage of this needed feature with the current way that it has been implemented.
Thank you for reaching out!
In order to set up proxy voting for only your employees, you can create an internal-only portal with just your colleagues as the portal users. Then enable proxy voting in this new portal. Your sales/services teams can use this new internal portal to view ideas, vote, submit new ideas, and create proxy votes as well.
A little background on portals in Aha! — you can create multiple portals for each workspace/product. The only differences between the portals are their settings, and the users you invite. You may want to create different portals for different audiences, with the settings appropriate for those users. Ideas from multiple portals will flow into the same product — where Aha! users can manage and prioritize them all together.
Let us know if that enables you to use proxy voting or if we can help any further!
Update: I just read Kelly Sebes explanation in the comments from April 30th and it "clicked" for me! Yes, we can now make this feature work for our company. We'll setup an internal only portal that includes the customer submitted ideas and votes and give that a try. Thank you!
We are running into the same situation. I searched for a duplicate idea before submitting a new one and found the idea that articulates exactly what we need as "already exists". We too have a private idea portal for our customers linked with our customer portal and SSO setup . We'd love to enable proxy voting for only our employees to vote on a customers behalf. I accidentally turned it on a few months back before realizing it was for "internal only" portals and a customer used the proxy voting to add additional votes under their own company. This would be an exciting feature for us if we can limit it to our employee domain on a private portal, that our customers can access. It's important for our customers to see the total vote count in one spot and to communicate what has been shipped. Thank you
I don't think that 'already exists' accurately reflects the status of this idea as it would involve creating a new portal specifically for internal users. A better solution would be to add a checkbox for whether the proxy voting would apply to all users or just those with email domains which have already been stipulated as employee/partner.
+1 on Jon's comment below. It seems inefficient to have employees manage the use of two portals, especially when we only have a single SSO configuration.
I would also encourage reconsideration of this feature implementation as it doesn't aptly solve for our use case either.
Amanda, that is exactly right! Create a new 'internal' portal for proxy voting and only invite your employees and partners to that portal. The same ideas will be available in both the new internal portal and your existing customer portal.
So I can create a different Ideas portal in which only employees and partners can proxy vote on ideas that customers and partners create in our existing Ideas portal?
I don't believe the response provided is a good option at least not for us. Administering multiple portals and having employees remember to use a separate Portal seems extremely inefficient when we already have a perfectly good way to designate who an internal employee is with just one portal.
We have developed multiple ways to utilize the ideas portal for internal/external users including inside the product which would not work to have a separate portal. Authentication also happens through our content management system which streamlines how a user accesses the portal today.
Please reconsider how you are implementing this feature.
Thanks for creating this idea, Jon. We're in the same situation, unfortunately.