A channel (approved AI interface) is where an identified person reaches a Role Assistant — Microsoft Teams, Slack, the AI Fabrix UI, Microsoft Copilot, ChatGPT connectors, or an embedded web experience. Channels are tenant assets: install once per environment, then expose Assistants that admins have made available for Business Roles.
The interface provides interaction. AI Fabrix retains the governed business capability. Changing ChatGPT, Copilot, Teams, or another interface does not redefine the Business Role, authority, or Evidence model.
What this shows: A person reaches a Role Assistant through an approved AI interface such as ChatGPT, Copilot, or Teams. The interface carries conversation; the Role Assistant returns governed results, questions, and completed work.
What this is not: ChatGPT or another interface executing enterprise work, granting authority, or replacing the Role Assistant.
Configure next: Conversation-first work for the request loop.
Why it matters
Enterprises do not want users to build bots, wire APIs, or paste prompts for every department. AI Fabrix generates Role Assistants from Business Roles — Sales Manager, Customer Success, Finance Controller — with context, capabilities, approvals, and Evidence rules bound to that role.
Users do not configure resources, capabilities, permissions, or channels. Admins make Assistants available for roles and connect channels. The platform enforces Operational Trust on every request.
How Assistants relate to roles
Business Role
↓
Platform generates candidate → validate → Make available
↓
Users with that role see the Assistant on approved channels
Example:
Sales Manager role → Sales Assistant
Customer Success role → Customer Success Assistant
The Business Role bounds what work may be requested (capabilities, approvals, Evidence). Dimensions and Operational Trust bound which records may appear. The channel only delivers the interface — it does not grant data or authority.
Do not create one Teams or Slack app per Assistant. One channel installation can serve many role-based Assistants.
Delivery flow
1. Discover roles ready for AI
2. Admin activates AI for selected roles
3. Admin connects the channel once
4. Channel is verified
5. Users with the role see their Assistant
6. Every request runs under platform governance
7. Evidence is collected from approved work
If Teams is not connected, admins see a clear action to connect Teams — not a developer error message.
Who does what
| Responsibility | Business owner | Admin | Integrator |
|---|---|---|---|
| Define business roles | Yes | Sometimes | No |
| Compile role-based Assistant | No | No | No (platform) |
| Activate AI for role | Approves | Yes | No |
| Connect Teams / Slack / Copilot / ChatGPT / Claude / Web | No | Yes | Supports |
| Store credentials securely | No | Yes | Supports |
| Approve external app in provider tenant | No | Yes | No |
| Use Assistant | Yes | Yes | Yes |
| Enforce permissions at runtime | No | No | No (platform) |
Admin activation: Connect assistant channels. Integrator hub: Deliver assistant channels. Per-channel Builder install: Slack, Teams, Copilot, Copilot Studio, ChatGPT, Claude.
Choosing a channel
| Channel | Best for | Manual approval often needed |
|---|---|---|
| Microsoft Teams | Enterprise chat, notifications, and micro-tasks (Ask / Approve) | Often (tenant admin) |
| Slack | Chat, notifications, and micro-tasks | Yes (workspace admin) |
| Microsoft Copilot | Microsoft 365 conversation experiences | Often |
| Copilot Studio | Custom agents that call governed Role Assistant tools | Often |
| ChatGPT | ChatGPT Enterprise / connector models | Often |
| Claude | Claude Team or Enterprise custom connector | Often |
| AI Fabrix UI | Operator recovery, Assistants evidence views, and temporary Review Workspace when rich review is required — not the default daily home | No |
| Web Embed | Customer portal or website widget | Website owner deploys embed |
Conversation channels are preferred for everyday Role Assistant use. The AI Fabrix UI supports operators and rich review; it is not where most employees should live.
What channels must not do
Channels must not bypass platform governance, call enterprise systems directly, decide permissions, or store business secrets in install packages. Users should see simple terms — Assistant, Role, Channel, Approval, Evidence — not internal platform jargon.
If a user's channel identity is not linked to an enterprise account, the Assistant must not access business data. The user should be told to contact an admin or complete identity linking.
Enterprise MCP parity
Approved external AI clients use the same governed tools as the portal and channels: they can begin work, check status or continue, present a human decision, and explain an outcome with Why?. They are not a parallel automation stack, and the same human interaction contract applies across conversation, Work, and Enterprise MCP. See External AI and Enterprise MCP.
Recommended first release
Focus on:
Teams chat, notify, and micro-tasks
Slack chat, notify, and micro-tasks
AI Fabrix UI for Assistants evidence and temporary Review Workspace
Customer-visible channel name and description
Secure credential flow and admin approval
Inbound request validation and audit evidence
Defer voice, meeting join, SMS, one app per Assistant, anonymous business access, and fully autonomous execution. Meeting transcripts belong on document storage with metadata validation — not as a channel install shortcut.
Limits
Channel capabilities, provider approval rules, and identity linking behavior evolve with platform and vendor policies. Confirm supported channels and certification requirements for your tenant before production Role Assistant pilots.
Copilot, ChatGPT, and Web Embed deployments vary widely by customer workspace governance — treat matrices above as planning guidance, not guarantees for every tenant.