Bot Identities
A bot identity represents an agent inside a workspace. It gives automated work a visible owner, configuration boundary, channel setup, and review trail.
Why Identity Matters
Bot identity answers practical questions:
- Which workspace does this bot belong to?
- Which channels can reach it?
- Which tools and prompts shape its behavior?
- Which operations and artifacts did it create?
- Who can modify or remove it?
This keeps agent work understandable to the team and auditable after the fact.
What A Bot Owns
A bot can have a display name, profile image, channel bindings, runtime configuration, prompt settings, and tool availability. The bot acts inside the workspace boundary and should be configured for the team's actual workflow.
Good Bot Setup
- Use names that match the bot's job, not generic labels.
- Keep one bot's channel bindings focused on one team or workflow.
- Review tool availability before enabling high-impact actions.
- Refresh profile details when the bot changes role or audience.
Media To Add
- Screenshot: bot list with multiple bots and status indicators. It helps admins understand bot inventory. Source: workspace settings bots page.
- Screenshot: single bot settings page with identity and channel areas labeled. It helps admins configure a bot safely. Source: test workspace bot detail route.