When an Idea is submitted an admin can choose if the idea is visible in the portal it was created and/or other portals within the workspace.
Fabion Kauker
Nov 21, 2025
Sure here are my three usecases:
The current workspace is for product development of “Arrow” out network planning product. We want to be able to support internal users submit ideas for features and improvements.
We want to share the same workspace with external customers so that they can do the same as above.
We want to also be able to collect a back log of technical clean up from internal users.
Each of these should only have the ideas visible from the portal that created them. For separation of context and also data leakage across internal and external teams.
Since Aha! has set it so that ideas are housed in workspaces vs in portals, there currently is no way to filter visibility based on portal. We'd like to see an option for "Visible to portal user" under the Default Visibility dropdowns. If we have one client-facing portal and one internal-facing portal in the same workspace, we don't necessarily want the ideas submitted in one portal visible to users in the other. Example: For clients to vote on ideas other clients have submitted in the client-facing portal, we need to set visibility of those "to all". Now those are visible in the internal-facing portal, and our end users would prefer to not have the client-facing portal ideas cluttering the internal-facing GUI. We can easily set ideas created by employees to visible by employees, but can't figure out the client-facing ones.
Hi! We want to have different portals for internal and external stakeholders. In the past we were able to configure the visibility with the existing visibility type. As we know need to change the visibility to 'visible to all' so we can make use of the Salesforce integration, we do need another way of choosing if an idea is visible for different stakeholders. Ideally, we would be able to define whether the idea is enabled for the internal and/or the external portals.
We want to have one portal for our customers (with login), and another one for the community edition users (public). We want to show some ideas on the customers portal, so those ideas should not be visible on the public portal.
We wish to vet the ideas through an internal portal prior to opening them up for outside review. While we could move the idea all around to different workspaces, keeping the two portals in the same workspace reduces work.
Who would benefit? PM Team, Aha Ideas admin What impact would it make? Improved publishing of Ideas in portals How should it work? When changing visibility of an Idea, I also want to be able to select which portal the Idea should be visible in and...
Mats Hultgren
almost 2 years ago
in Ideas portal
0
Planning to implement
4
MERGED
Ability to remove an Idea from a portal when more than one portal is active
Merged
Currently I have a workspace with two portals. When an idea is created and made visible to "Employees" it will show in both. One portal is meant for Customers and Employees (using the visibility settings), while the second portal is a subset of em...
Chris Eichermüller
almost 5 years ago
in Ideas portal
0
Planning to implement
Sure here are my three usecases:
The current workspace is for product development of “Arrow” out network planning product. We want to be able to support internal users submit ideas for features and improvements.
We want to share the same workspace with external customers so that they can do the same as above.
We want to also be able to collect a back log of technical clean up from internal users.
Each of these should only have the ideas visible from the portal that created them. For separation of context and also data leakage across internal and external teams.
Since Aha! has set it so that ideas are housed in workspaces vs in portals, there currently is no way to filter visibility based on portal. We'd like to see an option for "Visible to portal user" under the Default Visibility dropdowns. If we have one client-facing portal and one internal-facing portal in the same workspace, we don't necessarily want the ideas submitted in one portal visible to users in the other. Example: For clients to vote on ideas other clients have submitted in the client-facing portal, we need to set visibility of those "to all". Now those are visible in the internal-facing portal, and our end users would prefer to not have the client-facing portal ideas cluttering the internal-facing GUI. We can easily set ideas created by employees to visible by employees, but can't figure out the client-facing ones.
Hi! We want to have different portals for internal and external stakeholders. In the past we were able to configure the visibility with the existing visibility type. As we know need to change the visibility to 'visible to all' so we can make use of the Salesforce integration, we do need another way of choosing if an idea is visible for different stakeholders. Ideally, we would be able to define whether the idea is enabled for the internal and/or the external portals.
We want to have one portal for our customers (with login), and another one for the community edition users (public). We want to show some ideas on the customers portal, so those ideas should not be visible on the public portal.
In this case, I recommend having new ideas default to 'visible to employees' and then after review, update the idea to 'visible to all'.
We wish to vet the ideas through an internal portal prior to opening them up for outside review. While we could move the idea all around to different workspaces, keeping the two portals in the same workspace reduces work.