Microsoft Teams and Agent Email
Bring the AI team into the channels people already use while keeping identity, routing, external communication, and cleanup governed.
Microsoft Teams deployment
The Setup wizard creates a tenant-specific Teams package for the selected RapidClaw product and publishes it to the customer's Teams app catalog. The package uses a product-specific identity: RCOC for RapidClaw for OpenClaw, RCRS for RapidClaw for RapidStart Apps, or RCBC for RapidClaw for Business Central.
- Teams readiness is not marked complete until catalog publication and the message-forwarding path are functional.
- Teams conversations use the same agent, model, connector, permission, approval, and audit boundaries as Command Center.
- Publishing the app does not authorize every tenant user or every agent capability.
- Use the Microsoft Teams page in Command Center to review readiness and rollout status before expanding access.
Teams is a channel, not a separate agent runtime
The same RapidClaw deployment serves Command Center and Teams. A conversation in Teams does not bypass Command Center configuration, product policy, approvals, or Emergency Stop.
Create agent mailboxes in Command Center
Email infrastructure is part of RapidClaw Base, but mailboxes are not created during the deployment wizard. Create and manage them later from the shared Email page in Command Center, only for agents that need an email identity.
- Open Email and select the agent that needs a mailbox.
- Choose from the verified tenant domains available to the deployment.
- Review the proposed address and create the mailbox through the governed flow.
- Keep the mailbox in test mode and send a test message before enabling broader communication.
- Confirm the agent's external-message policy and approval requirements.
- Use the controlled deletion flow when a mailbox is no longer needed. Existing mailboxes are not edited in place.
Inbound and outbound email safety
- Inbound content passes through a controlled reader and sanitization path before an actor agent processes it.
- Sending, replying, forwarding, and other external communications remain subject to policy and approval.
- Test mode provides a safer place to validate routing, instructions, and expected responses.
- Created and product-seeded mailboxes are tracked in the deployment manifest so reset can remove them safely.
Product-specific email behavior
| Product | Email behavior |
|---|---|
| RapidClaw for OpenClaw | Administrators may create Base mailboxes for selected agents through Command Center. |
| RapidClaw for RapidStart Apps | Selected CRM Agent Packs may recommend mailbox-enabled agent definitions. The operator still creates and tests each mailbox through the shared Email page. |
| RapidClaw for Business Central | Uses the shared Base email capability but does not seed Business Central-specific mailboxes. |
Troubleshooting checklist
- If Teams is unavailable, check tenant-catalog publication and forwarding readiness in Command Center before reinstalling anything.
- If some users cannot access Teams, review the intended rollout and tenant app policies rather than changing agent permissions blindly.
- If inbound email behaves unexpectedly, return the mailbox to test mode and review reader sanitization, agent instructions, routing, and approvals.
- If an outbound message is waiting, inspect Approvals and the external-communication policy before retrying.