Locking fields inside the Business Case tab in a project.

[arohm]

Hello!

I am looking for some advice with locking critical fields in the Business Case tab (like Strategic Priority, Primary Goals, In Scope/Out of Scope, etc.) to prevent unauthorized edits and reduce scope creep. Ideally, after a project has been submitted and has moved beyond the planning phase these fields can only be editable by a small group of people (managed by group membership)

What is the easiest and cleanest way to go about this?

[Uncle Rob]

Locking / unlocking based on field values is super easy via UI Policies.
Locking / unlocking based on ROLE is significantly more difficult, and requires ACLs

[arohm]

So should i do both? Lock them with a UI policy but then use an ACL that unlocks them based on group? or do it all in an ACL.