Free · runs in your browser

Can your approval rule be bypassed?

Choose how many approvals a change needs and how long they last. AtlaSent’s policy engine then tests self-approval, missing, repeated and expired approvals, and shows any scenario that gets through.

Test a rule Try a weak rule

This runs AtlaSent’s real policy rule engine in your browser against a few made-up approval scenarios. It tests one approval rule on its own. It does not contact AtlaSent, look at your systems, or issue a permit.

Describe your approval rule

What the approval rule decided

Not tested here

Whether the change that runs is the exact change that was approved. A live AtlaSent runtime binds an approval to the change and refuses a permit whose change differs.
Whether an approval was given for this action and environment, rather than a different one.
Who is allowed to be a reviewer, and whether their identity was verified.

In a live AtlaSent organization a missing approval may put the action on hold for approval instead of refusing it. A passing result here is not an authorization decision.

Your rule in AtlaSent’s policy format

Was this useful?

Already using AtlaSent?

Policy Studio’s Approval Tester runs the same kinds of scenarios against your organization’s own policy, evaluated by the AtlaSent runtime. It is a simulation: it changes no enforcement and issues no permit.

Is your real rule enforced like this?

This tests the rule as you described it. Whether production actually follows it is a different question: who can bypass it, approvals given outside it, and what actually ran. The fixed-scope $750 Production Change Control Audit reviews one workflow end to end. It is not a certification or an installation of enforcement.

Review the $750 audit → · See a sample audit

What you can do next

Check whether a real merged pull request was approved and tested on the code that shipped: free Change Check. Or answer five questions about your deploy path: free control self-check.

To enforce a rule like this before a deploy runs, start with the developer path. Enforcing it in a real organization needs separate setup and verification.

Engine: github.com/AtlaSent/atlasent-policies cli/src/engine/rules.ts @ 9f94cb3be1f1 (the public copy of the engine AtlaSent’s runtime uses), Apache-2.0.

Other free checks: Change Check · AI Permission Check · Change control self-check · all free tools