Team Bots
Team Bots act as permanent digital teammates within your organization. Shared across Slack, Microsoft Teams, GitHub, and the Plannix Console, they retain organizational context and execute collaborative workflows.
What are Team Bots?
A Team Bot belongs to a workspace rather than an individual account. Team members can mention the bot in shared channels or invoke it from PR discussions, and everyone on the team can inspect the bot’s execution history, terminal traces, and generated artifacts.
Team permissions and visibility
Control which team members have authority to trigger expensive jobs or approve write operations:
| Role | Chat | Execute Tools | Approve High Risk | Edit Config |
|---|---|---|---|---|
| Viewer | Read-only | No | No | No |
| Contributor | Interactive | Yes (Sandboxed) | Requires Admin | No |
| Admin | Interactive | Yes | Yes | Yes |
Multi-agent task distribution
Team Bots can split a large objective across specialized subagents—such as a security scanner, a unit-test generator, and a documentation compiler—synthesizing their results into a single coherent pull request.