Many humans, many agents
Permission parity
Permission parity is the rule that an agent may do what a person in that role could do and no more, and cannot read anything the delegating user cannot read.
Control sits with the person
When to use it
Use it in every shared deployment. The rule is simple and easy to explain to a security team.
What it prevents
Privilege escalation through delegation, where an agent inherits broader access than the person who asked it to act.
What the agent may domirrors the role
Read the shared driveElin canAgent can
Read the salary folderElin cannotAgent cannot
Delete a client recordElin canAgent asks first
Never more than the person. Sometimes deliberately less.
Where it is used
- Notion Agent and Asana: stated as the operating rule for Notion Agent, and as a core conceptual model in Asana’s engineering write-up on AI teammates
Sources
Related patterns: Addressable team member · Delegated identity
Worked through as a deck: Your newest teammate has a spend cap