If you have a user called Claude, then you just apply ACL as normal & you don't care if they're human or bot, right?
If you have a user called Claude, then you just apply ACL as normal & you don't care if they're human or bot, right?
That's why multiuser agents can be an issue.
The other way to do this, is to have claude installed for everyone, and any user's chat with claude uses their personal permissions via something like oauth delegation or AWS IAM role kinda things. But that, again, is complicated ACL logic living through the delegation of roles and access
So rather than having "Claude" installed as a god-mode user in all channels, you have 10 instances of a bot running, each with their own context and ACLs.
For example, you could set it so that the agent's ACLs become the intersect of the least privileged user in all the channels it lives in - you try to add a bot to the "Executive Bonus discussion" and get told
> You can't add AliceBot to this channel because AliceBot is also in #intern-onboarding alongside 'Johnny Appleseed' and Johnny doesn't have access to this channel. Would you like to create a new bot?"