Tools
Planning tools for safer agent decisions.
Use these prompts to prepare a first draft for discussion with the teams responsible for implementing and overseeing the agent.
Before you complete your permission plan: Use How to Decide What Your Customer-Facing AI Agent Is Allowed to Do to build a complete permission plan, and How to Decide What Your AI Agent Can Do on Its Own to assign independent authority, customer confirmation and employee approval.
Permission Design Playbook
Download the free 12-page guide to define AI agent permissions, approval rules, human handoffs, recovery and testing for one customer-facing task.
After you draft a plan: How to apply your permission plan in an agent platform explains how teams can translate the playbook into platform settings, workflows, approval checks and tests.
Permission Plan Builder
Turn one customer task into a permission plan your team can review, implement and test. Document intended authority, evidence, approval rules, recovery paths and tool-failure behavior in one working plan.
This browser-based tool does not require registration. It processes entered plan content in your browser and does not send it to PermissionByDesign. It documents intended authority; connected systems still need to enforce the rules.
Prefer a document-based process? Use the printable permission-planning worksheet.
Taking the plan into implementation? Browse agent permission-design resources for official guides, tutorials, authorization software and testing tools.
New to these terms? Read the permission design FAQ before choosing a tool.
Build your permission plan
Use the blank worksheet to prepare a first draft for one customer-facing AI agent use case. The PDF is designed for printing and handwriting. The Word version is designed for editing.
See a completed example
Review a fictional refund-and-return plan using illustrative policies and limits. Use it as a model for structure, then adapt every rule, approval path and technical control to your own business.
What the worksheet helps you decide
- Name the customer-facing task.
- List every action the agent might take.
- Mark each action as inform, recommend, act within limits, request approval or not permitted.
- Define routine limits with concrete conditions.
- Name the approval trigger for exceptions.
- Decide who or what approves the action.
- List the system evidence that records the decision.
- Write routine, exception and prohibited-action scenarios to test.
Approval request checklist
- Customer request summary.
- Action the agent wants to take.
- Policy or business rule involved.
- Reason the request exceeds routine limits.
- Relevant customer, order, account, or transaction evidence.
- Recommended decision and alternative options.
- Record of who approved, declined, or changed the action.
These tools are educational planning aids. They are not a substitute for technical controls, security review, legal advice, or compliance approval.
