1,000 scenarios for how teams govern AI agents
Worked examples, sorted by business function, of what an AI agent may do on its own, what waits for a person, and what it never gets. Each one names the controls it uses. Some depend on capabilities still in development and carry a Coming soon label.
Money, customers and people
Finance & Accounting
Payments, the close, treasury, budgets and payroll.
Sales & Revenue
Outreach, the CRM, quotes, contracts and renewals.
Marketing & Communications
Content, campaigns, paid media, social and the website.
Customer Support & Success
Ticket replies, refunds, privacy requests and escalations.
People & HR
Hiring, onboarding, compensation, employee relations and training.
Systems, risk and operations
Software Development & Engineering
Code review, releases, production systems and on-call.
IT & Security Operations
Identity, devices, threat response, SaaS admin and cloud.
Data, Analytics & AI Operations
Warehouse access, pipelines, agent-to-agent work, models and AI cost.
Legal, Risk & Compliance
Contracts, regulatory work, audit evidence, vendor risk and records.
Operations, Procurement & Facilities
Purchasing, vendors, inventory, facilities and projects.
Scenarios, not a feature list
Each scenario is how a team would set up one control. Some depend on capabilities still in development. Products named in a scenario are systems your team runs, named to make the example concrete. The policy applies to the AI agent's calls into them.
Set these policies up for your own agents.
Start with your own agents, your tools and the approvers you already have.

