---
title: "Comment by Ehsan on \"Design Permissions From the Handoff, Not the Org Chart (Including Your AI Agents)\" | Hashnode"
description: "Modeling who can touch a quote from the handoff instead of the title feels right, especially the AI draft role that can write but never send. How are you stoppi"
url: "https://hashnode.com/posts/design-permissions-from-the-handoff-not-the-org-chart-including-your-ai-agents/6b0077a09295df63f659305a/comment/6b01605045bbf7ac41924392"
---

[Discussion](https://hashnode.com/posts/design-permissions-from-the-handoff-not-the-org-chart-including-your-ai-agents/6b0077a09295df63f659305a)

Comment [Design Permissions From the Handoff, Not the Org Chart (Including Your AI Agents)](https://hashnode.com/posts/design-permissions-from-the-handoff-not-the-org-chart-including-your-ai-agents/6b0077a09295df63f659305a)

[Ehsan](https://hashnode.com/@ibuildinpublic)

[1h ago](https://hashnode.com/posts/design-permissions-from-the-handoff-not-the-org-chart-including-your-ai-agents/6b0077a09295df63f659305a/comment/6b01605045bbf7ac41924392)

Modeling who can touch a quote from the handoff instead of the title feels right, especially the AI draft role that can write but never send. How are you stopping crews from just sharing logins when the role is still a bit too tight on day one?
