Problem:
Currently, team member permissions apply to all bots on an account. There's no way to restrict a team member to specific bots only.
Use Case:
Agency managing multiple clients, where each client has complex internal teams. Different team members need access to different bots within the same account, but shouldn't see or edit bots for other departments/teams.
Current Workaround:
Set up separate sub-accounts per bot group and add each person as a team member on only the relevant account. This is functional but clunky to manage at scale, especially as more clients with complex internal structures are added.
Impact:
High priority for feature development. Not an immediate blocker for adoption, but will cause friction as the agency scales and adds more clients with multiple internal teams needing segmented access.
Requested Feature:
Granular, per-bot permission controls - ability to assign team members to specific bots rather than giving them access to all bots on the account.