Our policy engine is the foundation for flexible controls and permissions within your organization. This page provides an overview of how to author policies.
effect
determines if an activity should be allowed or denied based on the evaluation of the consensus
and condition
fields.
consensus
and condition
are composed of ergonomic expressions written in our policy language that must evaluate to a bool
. consensus
determines which user(s) may take an action (e.g. a given user ID). condition
determines the conditions under which the policy applies (e.g. signing with a specific wallet). These fields can be used alone or together.
OUTCOME_ALLOW
EFFECT_DENY
, the final outcome is OUTCOME_DENY
. This is also referred to as “explicit deny.”EFFECT_ALLOW
, then the final
outcome is OUTCOME_ALLOW
OUTCOME_DENY
. This is also referred to as
“implicit deny.” In cases of conflicts, EFFECT_DENY
always wins.