Policy Scope Basics

Policy scope defines how Beav3r should evaluate and route approvals for a project.

Why it matters

When you set up a project, Beav3r needs enough context to apply the right approval behavior to the actions coming from that project.

You do not need to model a full internal policy engine to get started. You only need to choose a setup shape that matches how you plan to use Beav3r.

Common setup shapes

The common setup shapes are:

• SDK-oriented usage
• integration or bridge-oriented usage for connected systems such as OpenClaw

How to choose

Choose the SDK-oriented path when:

• your app talks to Beav3r directly
• you are building approval checks into your own product or runtime

Choose the integration-oriented path when:

• a connector or bridge sends approval traffic on behalf of another system
• you want a prebuilt path such as OpenClaw x Beav3r

Expected result

After choosing the right setup shape:

• the project matches the way approvals will reach Beav3r
• your API key is used in the correct runtime path
• signer and integration setup are easier to reason about