What user action typically triggers an approval request in the Proof Platform?

Submitting a proof for review is the correct action that typically triggers an approval request in the Proof Platform. This process is fundamental to the way collaborative feedback and approval mechanisms operate within the platform. When a user submits a proof for review, it signals to the required stakeholders that the proof is in a state ready for evaluation and decision-making. This initiation allows designated approvers to assess the proof and either approve it or request changes, ensuring that all necessary feedback is gathered efficiently.

Other options like marking a proof as final involve a different context; this action indicates readiness for deployment rather than initiating a request for feedback. Subscribing for notifications relates to updates and alerts about changes rather than triggering formal approval processes. Inviting users to a project is a step in managing collaboration but does not directly relate to the approval cycle of a submitted proof.