Custom fields are a very important feature of Asana and can be a key way to align and track work across different teams in an organization. However, this can be negatively impacted when there are duplicate/contradictory/vague custom fields added to an organization’s library of custom fields.
There needs to be a way to permission only designated users to be able to add/edit custom fields in the organization’s field library.
Yes, this can be done with Field Admin permission to the custom field, but not with Editor or User permissions
Thanks,
Larry
I think that is unrelated to my question/idea. I was referring to the ability to add new custom fields to the organization-wide library of custom fields, that are then made available for anyone to use in their own project.
My understanding is that as long as a user is the admin of their own project, which in turn gives them the ability to add custom fields to that project, Asana also gives them the ability to add that custom field to the organization-wide library of custom fields.
We are trying to prevent users adding custom fields ad hoc to the organization-wide library.
Ok, I think you’re asking for more granular permissions than are offered so I unmarked my post as a solution. I think this request would require extra process and possibly permissions to implement.
I voted, @Michael_Barry! I agree that the current design makes it easy to add redundant custom fields and that in some use cases, it would be good to prevent their creation as you’ve described.
I added my vote as well @Michael_Barry
I think this is good and would help PMOs and Admin users to implement processes specific for custom fields which could have a positive impact on reporting, on project implementation and consequently a decluttering outcome.
