A form needs a clear boundary between fixed instructions and responses. Content-control locking can protect a particular value or label. Restrict Editing protects the document more broadly. These settings should follow the form's intended workflow, because protection applied too early can stop someone entering the required content.
Use Developer properties for a control's lock setting and Review for document restrictions. The simulator models those editing rules, but it doesn't encrypt a file or manage real passwords. Don't treat a practice protection toggle as a security boundary for sensitive data. You'll lock approved content, leave a response editable and protect a completed form. The final task removes a restriction before an authorized edit, then returns the form to its protected state.
The lock state follows the role of each piece of content.