A channel is where employees reach role-based Assistants — 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 every Assistant that admins have activated for business roles.
Why it matters
Enterprises do not want users to build bots, wire APIs, or paste prompts for every department. AI Fabrix compiles Assistants from business roles — Sales Manager, Customer Success, Finance Controller — with the right context, capabilities, approvals, and evidence rules already bound to that role.
Users do not configure resources, capabilities, permissions, or channels. Admins activate AI for roles and connect channels. The platform enforces governance on every request.
How Assistants relate to roles
Business role
↓
Platform compiles governed Assistant
↓
Admin activates role for AI
↓
Users with that role see the Assistant
Example:
Sales Manager role → Sales Manager Assistant
Customer Success role → Customer Success Assistant
The role determines business context, included resources, available capabilities, required approvals, evidence collection, and which channels may expose the Assistant.
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 / 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) |
Detailed install steps: Connect assistant channels. Technical delivery: Deliver assistant channels.
Choosing a channel
| Channel | Best for | Manual approval often needed |
|---|---|---|
| AI Fabrix UI | Default internal use | No |
| Microsoft Teams | Enterprise chat and notifications | Often (tenant admin) |
| Slack | Chat and notifications | Yes (workspace admin) |
| Microsoft Copilot | Microsoft 365 experiences | Often |
| ChatGPT | ChatGPT Enterprise / connector models | Often |
| Web Embed | Customer portal or website widget | Website owner deploys embed |
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.
Recommended first release
Focus on:
AI Fabrix UI for active role Assistants
Teams chat and notify
Slack chat and notify
Customer-visible channel name and description
Secure credential flow and admin approval
Inbound request validation and audit evidence
Defer for later: voice calls, meeting join, meeting transcript ingestion as a channel feature, SMS, one app per Assistant, anonymous access to business data, fully autonomous execution without approval.
Meeting transcript use cases belong on document storage datasources with metadata validation and governed retrieval — 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.