Documentation / Approvals

The right action. The right review.

Define review points before a bee starts work. Tool access and permission to perform a consequential action are separate decisions.

A little help. A whole lot of possibility.
01

Preparation before execution

Ask for a draft, proposed change, or action summary first. Review the target, content, and expected effect before approving the action.

02

Outside content is not an instruction from you

The application can hold risky actions after reading outside material. A message, webpage, or document should not be treated as authority to expand a task.

03

Scoped allowances have limits

Eligible allowances cover a specific tool and target for a routine or bot. Routine changes can pause them. Connected-app actions through Composio require separate approval rather than an advance allowance.

04

Configuration matters

Protection modes, exemptions, and logging are operator-controlled. Confirm the settings for your deployment instead of assuming that every control described here is enabled.

One good place to start

What could your first bee help with?

Choose a role. Give it a clear job. Build from there.

A little planning. A lot of possibility.

Build your bee team.

Choose the roles you need and give your future hive a first task.

Your teammates

Planning preview · Your brief stays on your device. No account is created and nothing is submitted.