System-wide way to lock custom field values for all users (including project admins)

Hi team

Use case:
We’ve started using Asana to house our risk assessments and have configured a separate view to show tasks of custom type “risk”.

Users select the likelihood and consequence from two single select dropdowns. That change drives a rule that populates the inherent risk rating for them based on the combination of likelihood and consequence according to our risk matrix. It works great!

Problem:
On a project-by-project basis, we can lock down the inherent risk rating custom field so that only project admins can update the inherent risk rating custom field value manually. The problem is that:

a) we need to implement that change manually for every single project, and
b) project admins can update the inherent risk rating value manually.. and they sometimes do, which means their risk ratings don’t match the likelihood and consequence ratings. :sweat_smile:

The ask:
Could Asana please implement the ability to completely lock (make read only) a custom field org wide to users. This would mean the custom field could only be updated by rules, Asana AI or other automations. Perhaps this could be selected in the field access settings (example below).

Thank you

Hi @G.White , I voted too!

In case it helps, you can add field restrictions (available on Enterprise plans) into your project templates so you don’t need to set this up each time.

2 Likes

@Richard_Sather ahh! Right you are! I hadn’t noticed that’d snuck in! :grin:

Thank you, great tip!