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
An agreed evaluation scope and confirmed integration version. Gateway, SDK, adapter, playground and binding screens are marked planned in the reviewed product navigation.
Steps
- Bind policy to the actor and protected action. Decide explicitly whether an unavailable check blocks the action or sends it to human review.
- 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
Distinguish detector failure, policy rejection and enforcement failure. A permit decision without a verified enforcement record is not proof that protection completed.