Claude Tag may need person-based access, not channel-based access
currently limits its AI by channel. A private channel gets one shared Claude, and public channels can also be set up with . Everyone in the channel talks to the same Claude, so one person can continue from where another stopped.
Admins choose which tools and data each channel’s Claude can use, and its context stays inside that channel. This is easy to understand, but it may not match how people actually work. People move across many channels, and their real data access usually does not fit neatly inside one channel.
A better design would make Claude act under the identity and of the person who tagged it. The same AI should give different answers to different people if they are allowed to see different data.
Key points
- uses the channel as the boundary for context, tools, and data access.
- Admins can decide what each channel’s Claude is allowed to reach.
- Channel-based access is simple, but it may not match real workplace .
- Person-based access would make the AI act with the caller’s own .
- Agent builders should design before adding broad .