A procurement team has fresh role definitions and approval requests. Use the configured record type, threshold and approver role in each task. The presence of an Approve button can't stand in for a permission, subsidiary scope or amount limit.
These independent tasks distinguish saving a rule, creating a pending order and recording a decision. A rejection should remain visible, while approval should not invent a receipt. Role tasks require the exact requested scope; granting all subsidiaries changes the result. Inspect the transaction state after the decision and keep the supported physical stage separate. The final question asks what the local context switch proves about real identity administration. It lets you rehearse a control boundary without claiming to assign users in a production account.