Skip to main content
Tenant ACL uses a deterministic engine to evaluate incoming requests. To determine if an action (allow, block, or redirect) should be taken, the engine follows these evaluation steps:
  1. Evaluation order (priority)
  2. Condition matching (signal)
  3. Match termination with monitoring mode exception

Evaluation order

The Tenant ACL evaluates rules in ascending order based on their priority number. Evaluation starts at the lowest number, priority 0, and proceeds sequentially. If two rules could both match a request, the one with the lower priority number will trigger first.

Condition Matching

For a single rule to trigger its action, it must satisfy the matching logic. This logic determines how the engine treats multiple values and multiple signal types: Any signal types not provided in a rule are ignored and do not impact the rule’s evaluation logic.

Match Termination

Tenant ACL applies the first match. Once a rule’s conditions are fully met, the behavior depends on whether the rule is in monitoring mode or not.