Members & Roles
Understanding the building blocks of your AI workforce: member types, roles, and configuration options.
Member Types
Every workforce member falls into one of three types, which determines their position in the hierarchy and expected responsibilities.
Top-level members who coordinate work and delegate to specialists. They have the broadest context and make strategic decisions.
Domain experts who handle specific tasks. They report to managers and may delegate to support members.
Task-focused members who handle specific, repeatable operations. They receive delegated work from specialists.
Member Properties
Each workforce member has several configurable properties that define their identity and capabilities:
| Property | Description | Example |
|---|---|---|
| role | Display name shown on the org chart | "Sales Manager" |
| responsibility | Short job description (1-2 sentences) | "Oversees sales pipeline and coaches SDRs" |
| level | Hierarchy position (0 = top-level manager) | 0, 1, 2 |
| tools | External integrations via Composio + built-in tools | Gmail, Slack, Calendar, Web Search |
| knowledgeBase | Reference materials (docs, URLs, PDFs) | Product docs, sales playbook |
| approvalPolicy | When to require human approval | auto, require, custom rules |
Hierarchy Diagram
A typical workforce follows a tree structure where work flows downward through delegation:
Configuring Member Tools
Connect to external services like Gmail, Slack, Calendar, CRMs, and more through Composio integrations.
- Email: Gmail, Outlook
- Calendar: Google Calendar, Outlook
- Messaging: Slack, Discord
- CRM: HubSpot, Salesforce
- Project: Jira, Linear, Asana
Standard capabilities available to all agents without external configuration.
- Web Search
- News Search
- Scholar Search
- Google Maps
- Memory Read/Write
Approval Policies
Control when and how actions require human approval:
Auto
Agent executes all actions immediately without waiting for approval. Best for low-risk, high-volume tasks.
Require Approval
All tool invocations require human approval before execution. Best for sensitive operations.
Custom Rules
Define per-tool approval rules. For example, auto-approve web search but require approval for sending emails.