Evaluation guide
Check access and controls
Test the intended access boundary before broadening use.
Confirm the enabled version and permissions in your environment. These guides do not announce a general release.
Before you start
A bounded evaluation scenario and a person authorised to approve it. No production execution or automatic approval is assumed.
Steps
- Separate the requester, planner, approver and executor. Bind approval to a specific plan revision; material changes require review again.
- Test both an allowed action and an action outside the assigned scope. Review access again when the user, source or policy changes.
- Compare the observed outcome with the expected result. Keep the relevant identifier and a redacted record so a colleague can review the same case.
Check the result
Compare the observed outcome with the expected result. Keep the relevant identifier and a redacted record so a colleague can review the same case.
If it does not work
If the target, approved revision or verification evidence is missing, stop the evaluation at that boundary. Record the gap rather than inferring permission.