Disable update of project settings fields that are awaiting for approval

Problem to solve

As part of two-person approval workflow, when a project settings change is awaiting for approval, we should not allow update of these project settings. This should apply to app controller, REST API and GraphQL API.

Intended users

• Cameron (Compliance Manager)
• Sasha (Software Developer)

User experience goal

Requests to update these fields should be rejected with appropriate error messages.

Proposal

Further details

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references