We use Aha! for all our product planning, however we currently do some financial estimates outside of Aha! which we don't want to share with the wider development team. This causes us to fragment our data and use permissions in other portals as the gate for the more sensitive data.
I would like to be able to define user groups, such as "Executive team", "Product team", "Development team" and be able to define visibility and write access of different fields for each of those teams.
This would restrict them from being visible in the details view and also prevent those user group from creating reports with those fields.
If we had this feature we could consolidate our product lifecycle planning into Aha!, including the more sensitive data.
Agreed - Our organization needs a way to restrict Team & Salary info related to capacity planning
Hi Jerimiah. Would your sales team be adding proxy votes through an ideas portal? If so, that would limit their ability to view or edit any other Aha! fields. Alternatively, if the sales team are Viewers or Reviewers in Aha!, they can actually add proxy votes, but not edit any other fields. Please reach out to our product success team if you would like any help exploring those options.
Without the ability to limit what some roles can do we are limited on expanding this to some of our sales teams. Case in point we would like to use proxy votes as a way to prioritize ideas by organization through custom fields but do not want the sales teams to edit any other fields on the ideas or in roadmaps.
We need to be able to manage permissions based on role in order to expand Aha! adoption.
I agree. We are using an Aha! workspace to manage our recruiting process. I was just looking for a way to restrict a custom field's view to a limited group of users or user types (Similar to your Executive Team example) for a "Salary" custom field or other confidential information.