Agent roles explained
How agent roles and identity work in Dailybot: naming, attribution, and visibility in reports.
In Dailybot, agents appear as first-class participants in standups and reports. Each agent has an identity (name, optional avatar) so the team can see who — or what — contributed.
Agent identity
When you connect an agent (via MCP, API, or workflow), you configure how it is identified: typically a display name and optionally an avatar. That identity is used in channel posts, reports, and digests so that "Agent X" or "Deploy Bot" is clearly distinguished from human team members.
Roles and permissions
Agents use the same permission model as the integration that connects them. For example, an MCP server or API client is tied to a Dailybot account or app; what that identity can do (post check-ins, read context, trigger workflows) is determined by that account's access and any scopes you configure.