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
over 1 year ago
in Ideas portal
0
Future consideration
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.