Ideas portals should not show ideas from other portals that share the same products

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. 

  • Suzanne Vaughan
  • Jul 9 2015
  • Future consideration
  • Attach files
  • Jeff Champagne commented
    16 Apr 06:04pm

    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:

    • Product/Workspace

    • Categorie(s)

    • Visibility setting

      • 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

  • Trent Peterson commented
    20 Feb 07:59pm

    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!!!!

  • William Nassauer commented
    30 Oct, 2019 09:16pm

    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.

  • Mark Fauntleroy commented
    19 Jun, 2019 05:10pm

    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.

  • Ronnie Merkel commented
    4 Apr, 2019 04:10am

    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. 

  • Guest commented
    27 Jul, 2018 05:26pm

    vote for being able to change the default setting for visibility in the portal

  • nick bunte commented
    28 Feb, 2018 11:55pm

    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. 

  • Melissa Klemke commented
    27 Nov, 2017 01:17am

    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...

  • Yevgeniy Pinchuk commented
    7 Apr, 2017 06:41pm

    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.

  • Kirsten Erwin commented
    31 Mar, 2016 04:46pm

    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. 

  • Guest commented
    9 Feb, 2016 06:08pm

    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.

  • Matt Lavallee commented
    16 Nov, 2015 09:31am

    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.


  • Admin
    Chris Waters commented
    10 Jul, 2015 02:50pm

    This can be done by marking the employees in one portal as "Employee/partner" and marking their ideas as "Employee only". This will work regardless of the portal type. In fact you can have both employees and non-employees in the same public portal and still have some ideas hidden from the public (the will be marked as "Private" in yellow).

    Ideas belong to products - portals are just a way to view them. We are unlikely to create a relationship between portals and ideas so that ideas are also restricted by portal.

  • Guest commented
    10 Jul, 2015 08:06am

    This is a very real issue I'm coming up against at the moment.  If you could find a way to ensure our clients can only see ideas generated by other clients (not employee ideas) that would be a great help.  We have some fairly sensitive internal ideas (involving extra charges...) that I don't want clients to freak out over before we've had a chance to figure out the detailed positioning/messaging...

  • Avatar160.e35e46fe62a53e488ef9451dd1d3432e
  • Avatar160.e35e46fe62a53e488ef9451dd1d3432e