---
canonical: "https://yuanhaochen.dev/notes/enterprise-agent-permission-boundaries"
path: "/notes/enterprise-agent-permission-boundaries"
section: "Notes"
title: "Enterprise agents: where permission boundaries decide the category"
language: "en"
agentUse: "summary, retrieval, citation, hiring evaluation"
---

# Enterprise agents: where permission boundaries decide the category

Why enterprise-agent adoption is often decided by ownership, approval, rollback, and audit before raw autonomy.

The adoption cliff

Many enterprise-agent demos work until someone asks who is allowed to approve, write, undo, or explain the action. That is not a minor implementation detail. It is often the real product boundary.

The system can look intelligent while still being unusable if the organization cannot see where authority lives.

The map that matters

The useful market map is not just a list of agent vendors. It is a map of jobs, permissions, exception paths, audit requirements, handoff moments, and the cost of a quiet mistake.

The strongest wedge may belong to the team that makes a narrow action inspectable and reversible before it makes the assistant more autonomous.

What I would test

I would start with workflows where the proposed action is valuable but not safe to commit silently: knowledge-base updates, diligence notes, document routing, CRM changes, and internal research handoffs.