Skip to Main Content
Status Unlikely to implement
Categories Account settings
Created by Guest
Created on Oct 15, 2014

Custom Fields Permissions

When creating custom fields for ideas or features we need ability to select which user group has rights to edit it. We created a field named owners, with multiple select options from which a product owner can select several names of people that own the idea in our company internally.

  • Attach files
  • Haddon Fisher
    Reply
    |
    Nov 19, 2020

    This is not really a "nice-to-have" if you want people to be able to rely on Aha as a source of truth, which is why all of the other roadmapping tools I have used support this on day 1. Sure, I can just cut off someone's finger every time they change something they're not supposed to, but it would be a lot simpler (and less bloody) if we could just prevent them from editing in the first place.

  • Bernie Mulcahy
    Reply
    |
    May 8, 2020

    field level permission is needed for some of our custom fields. For example, we have added some custom fields that hold revenue information. That information should not be available to everyone in the organization.

  • Guest
    Reply
    |
    Apr 14, 2020

    Please this will help alot!

  • Guest
    Reply
    |
    Aug 15, 2019

    I just need to restrict access to one custom field, all the others are important all permissions to access. The specific custom field I am trying to restrict for Ideas is the concept of Priority which only I, the Product Manager, should be able to set

  • Marina Reyna
    Reply
    |
    Jan 22, 2019

    The work around process is not feasible for a large company.

  • Ron Yang
    Reply
    |
    Nov 25, 2015

    Hi Antonio, thanks for the request. As you may know, we currently have 4 levels of user permissions (Product owners, contributors, reviewers and viewers), which different levels of access. Adjusting user permissions would be one way to do this (ie., Reviewers and Viewers do not have access to custom fields).

    One workaround (outside of the software) is to implement the process that only the specified "owners" are allowed to make edits to areas that you've mentioned.

    At the moment with our current priorities, we do not have plans to add another level of permissions around editing rights. 

6 MERGED

Permission-restricted custom fields and tables

Merged
In order to scale, we need the ability to restrict the a user's ability to edit custom fields and custom tables on a record (example: XXX field on a feature).We should be able to configure specific custom fields and custom tables so that they're r...
Marina Reyna about 5 years ago in Account settings 0 Unlikely to implement