If you create two private (or public) ideas portals and both have product A and product B, any ideas created in either portal are visible in the other.
In this scenario, I want one portal for employees and one for customers. I do not want customers to see the ideas from my employees. I have no way to prevent this unless I make the portal public and create all customers as public portal users and my employees as private portal users. This is not desirable as I want a private portal for my customers.
Agree & upvote. The portal user view should only show ideas submitted from the origin portal. Since each portal has a unique URL, I can't think of a reason to share view of combined ideas created in distinct portals. This strikes me as a bug.
Agree with comments in this thread, we need to be able to manage ideas at a portal level within a workspace. For users of a portal to see ideas from another portal adds no value to them. We would also like to be able to customize the layout based on portal.
Not having this pretty much defeats the entire point of having multiple ideas portals. Like many commenters and the original poster, we would want to be able to have, at a minimum, one portal for internal teams, and another for external customers. Even more granularity within and without the company would also be valuable.
Very disappointed that a team of product managers supposedly building Aha! did not take this in to consideration. This seems like an essential.
This is an absolute must. We currently have a portal used by our internal employees and contractors, and wand to expand and add a second portal to our customers. We obviously can't have the already-existing internal ideas visible to the customers, as they include a lot of the back-office activities the internal teams use in the product.
I'm evaluating Aha right now - we have enterprise customers who would not want their ideas being visible to others, and who do want to look at the status of ideas that they have submitted (and have been submitted by other users within their company). If Aha could do this then our selection process would likely be over.
This is defeating the purpose of creating a multiple ideas portal for a single workspace if the ideas from portal A is being seen in portal B.This feature needs to be expedited for change.
I agree with many comments on this thread. I'd like to be able to manage ideas WITHIN a portal group. Group A should only see ideas submitted by Group A. However, the way you have it set up now, if I create a portal for Group A, Group B and Group C AND you provide access to comments, all groups will see each others comments.
Aha! support has suggested that the only way to create different comments sections is to create different workplaces for each. So Group A has a workspace and a portal, Group B has a workspace and a portal, and so on. Not only does this create additional work in create a new workspace for each, but it takes away the efficiency for my product management team of going into a single ideas board so they can efficiently triage the ideas as well as analyze the whole spectrum of from the portals in one place.
I would like the ability to toggle this on/off per product. Or better yet, give me much more granular control over what ideas appear where. I'd like to control if an idea appears on a specific portal based on:
Essentially, I'd like to customize the visibility based on a set of rules. Right now, its all or nothing across ALL portals. That doesn't allow us enough flexibility when we're running pre-release programs
We have a similar need. We would like to run and manage initiative level focus groups with separate Ideas portals. Each group would have a small number of internal and external stakeholders. The conversation (ideas & comments) would be focused around the initiative, and the product owner and design leads would be responsible for reviewing the ideas and keeping the conversation going. We have tried having a product level feedback group, but it lacked focus and was difficult to manage and track. This seems like an easy ask: add a setting on the focus group "Only view ideas submitted from this focus group" It's got to be a simple query tweak... so, please!!!!
This is a critical enhancement that we require as well. I have seen this same idea in other posting marked "unlikely to implement", so I'm glad this one at least says "future consideration". Here's to hoping.
Exactly the idea I've been looking to vote up. However, I would also add that a single product should be able to have multiple portals, where each portal can have it's own Ideas form layout.
This request exists in at least 12 different ideas over a few yeary that I can see and has hundreds of votes. It seems pretty prevalent that the voice of customer is asking for the capability to limit idea visibility by portal and product. Many are using an internal intake pipeline and an external customer intake pipeline. One would not want external customers to view internal portfolio submissions even if they were for the same product.A pretty straightforward scenario and since the portal name is an available field in the record adding a filter at the portal level should be a quick win.
The workaround to designate user as employee/customer type to limit visibility does not address this use case so please don’t respond with that as an option.
vote for being able to change the default setting for visibility in the portal
Would like to simply segment ideas to portals. We have a group of customers in an "early adopter" program with a specific portal. We need a way to segment beta and early adopter customers from others.
I'd also like to be able to have these with custom layouts, one group of questions we might ask one audience would be different to others...
Just came up against this issue this week, the funny part is no where in the literature or during my initial discussion with representatives was this issue brought up. After setting up portal visibility permissions and filters, you find out that visibility is controlled by the product line. If all portals are tied into a product line, than why have portals in the first place? I do not think it is over the top to expect to be able to separate multiple client portals which use the same product. Sort of feels like a feature that was implemented but not developed and integrated thoroughly into the rest of the product.
Additionally I feel like Aha could improve its disclosure on the issue in its literature, on boarding and support systems. When I spoke to a representative she was reluctant to admit that the portal functionality was lacking. It took several minutes of pressing the issue for her to admit that portals are essentially irrelevant for ideas as the product line will completely over rule the rest of the settings. Looks like it is the submit only option for us, until Aha figures out how to allow proper segmentation by portal.
We absolutely need this idea. We have a single product used by multiple clients. There are some customizations per client so they shouldn't see each others ideas.
Our only solution right now seems to be to have Ideas as submit-only and create a separate notebooks, filtered by email domains, so clients can track their ideas, but that's not ideal.
This would be valuable for us. We have different constituencies of users, plus employees/partners. The described workaround does not address this, and our only option will be to limit portal access to a single group and use email for the others.
Hi Chris -
This somewhat contradicts your own idea that we are also needing:
There are real scenarios for segregating (at least for user experience issues) sets of ideas based on the audience.