Skip to Main Content
Status Unlikely to implement
Categories Product
Created by Guest
Created on Mar 31, 2015

Granular Permissions for Components

It would be beneficial to Product Line Managers and Product Managers if individual custom components could be hidden from some individuals. This is useful when adding sensitive financial data or other secure information. If the Product is shared for Reviewers to see, they would see all components. We would like to be able to hide some of those components from specific users.

  • ADMIN RESPONSE
    Jan 5, 2016

    As you already know, we currently have 4 tiers of users permissions within Aha! (product owners, contributors, reviewers and viewers). We have spent much time gathering feedback from the community in constructing these permission levels. We don't currently have component level permissions, but one workaround would be to create a new Product and include some of the more secure information within a product that only some users have access to.

    At this time, we do not have plans to make changes to the user permissions model based on community feedback and our current goals and initiatives.

  • Attach files
  • Bill Sanders
    Reply
    |
    Sep 19, 2022

    Agree with the comments below. The ability to hide or restrict access to certain things in a workspace is absolutely necessary to maintain confidentiality of the product development lifecycle. Allowing customer and staff (non-PM or non-Dev) is an great help. Simple restrictions are the best of both worlds.

  • Sarah Steiner
    Reply
    |
    Dec 23, 2020

    We would love this functionality. Please reconsider the designation of unlikely to implement. Thanks.

  • Admin
    Austin Merritt
    Reply
    |
    Jul 18, 2017

    Hi Matt, many customers who are managing client work in Aha! will create products which are client-specific. This works nicely in the scenario you mention since navigation can be customized per product: https://support.aha.io/hc/en-us/articles/206283793-Customize-your-Aha-navigation. So you could add or remove sections as needed for each client.

  • Guest
    Reply
    |
    Jul 18, 2017

    We use Aha with our customers directly. Aha is awesome for us, but overwhelmes our clients. It would be really handy to be able to disable the components that we aren't using for them. For example, some clients we do strategy, releases, ideas, features etc for, but others we only do releases and features. Maybe we'll need to do a customised UI.

  • David Kettinger
    Reply
    |
    Jul 14, 2016

    Similar to this, but perhaps not as granular - we would like to be able to restrict access to strategy information within the Reviewer and Viewer levels.  Alternatively being able to configure access/no access to strategic information at the user level would work too.  We have contractors who work with our team and we'd want them to be able to see our feature and release information, but not all of our market and competitive intelligence under the strategy.

  • Elina Hu
    Reply
    |
    Jun 10, 2016

    We're hoping to use Aha! with both our internal team (account managers, sales etc.) and customers. Our use case is that we want to allow our internal team to post private comments, but NOT have access to all the exact release dates, etc. Currently the reviewer view allows commenting, but also reveals a huge amount of info that we want to keep within just the product org, since that info is constantly changing

  • Guest
    Reply
    |
    Nov 18, 2015

    would be good to in a sense turn of top menu items for some users. e.g. no features for some.

5 MERGED

Ability to define navigational permissions on a per role basis

Merged
This would be beneficial because not all of the roles need access to all areas of planning and strategy until those areas are more refined. This could also be mitigated by implementing a private section where one could brain-storm, keep notes on p...
Patty Dennis-Jones over 5 years ago in Epic 0 Unlikely to implement