Core principles
- A conversation provides intent and context; it is not unlimited authorization.
- Personal, team, company, and executive identities have different access scopes.
- Delegation follows visible reporting relationships.
- Boundary-crossing tool calls are reviewed before execution.
- Risky or ambiguous exact actions pause rather than silently executing.
- Approvals are one-use decisions, not blanket permissions.
- Durable runs, action reviews, delegation records, and receipts preserve an audit trail.
- Secrets stay out of prompts, chat, screenshots, templates, and Emberbase.
Identity and access boundaries
Assigning a channel, connector, or reporting line never overrides these access checks.
Review before execution
Automatic review evaluates the exact proposed tool call. It can approve, deny, or require a human. If the action changes after review, the approval no longer applies. Delegated instructions receive stricter authorization treatment because another agent—not the human—authored the handoff. See Automatic review and escalations.Human decision points
Use a human decision for:- external messages and customer-facing posts
- destructive or permission-changing actions
- financial or legal commitments
- public disclosure or credential-sensitive operations
- workflow steps where policy requires an accountable reviewer
- ambiguous actions that do not clearly match the user’s intent