Platform admin guide to activate role-based Assistants and connect communication channels (Teams, Slack, Copilot, ChatGPT, Claude, or the built-in UI). No developer workstation steps on this page.
Prerequisites
- Tenant ACTIVE (First session checklist complete)
- Business roles defined and approved for AI use
- Provider tenant or workspace admin available when external app approval is required (Microsoft 365, Slack, ChatGPT workspace, Claude Owner)
Where it happens
- Controller portal — activate AI for roles, view which channels are connected
- Microsoft Teams admin center, Slack app management, ChatGPT workspace, or Claude connectors — approve apps when the provider requires it
- Integrators — complete channel install how-tos after you confirm which roles to activate (see integrator guides below; no developer workstation steps on this admin page)
Steps
- Review roles ready for AI — identify which business roles should expose Assistants.
- Activate AI for each selected role — confirm scope, approvals, and evidence expectations with business owners.
- Choose channels — prefer conversation channels employees already use (Teams, Slack, Copilot, ChatGPT, Claude). Use the AI Fabrix UI for operator recovery and temporary Review Workspace — not as the default daily home. See Assistant channels.
- Connect each external channel once — not one app per Assistant. Set the customer-visible channel name with your integrator.
- Complete provider approval when prompted — Microsoft tenant admin for Teams or Copilot; Slack workspace admin for Slack; workspace admin for ChatGPT connectors; Claude Owner for Team or Enterprise custom connectors.
- Confirm secure configuration — credentials in the platform vault; no secrets in email or chat.
- Request integrator verification — integrator confirms inbound validation, identity mapping, and probe (see integrator guides below).
- Pilot with real users — users with the active role should see only Assistants they are entitled to.
Integrator install guides
What done looks like
| Signal |
Meaning |
| Role shows active for AI |
Assistant compiled and eligible for channels |
| Channel shows connected |
Provider install and platform config aligned |
| Test user in role sees Assistant |
End-to-end path works in UI or chat |
| Approval recorded |
Who approved which provider tenant and when |
Channel-specific admin notes
| Channel |
Admin focus |
| AI Fabrix UI |
Activate roles; operator views and temporary Review Workspace — not the default employee home |
| Teams |
Tenant app approval; note Microsoft tenant ID |
| Slack |
Workspace admin OAuth approval; signing and bot credentials via integrator |
| Copilot |
M365 extension approval; Entra tenant alignment |
| ChatGPT |
Workspace or connector approval; prefer OAuth over static keys |
| Claude |
Owner adds the custom connector; members authenticate and enable it |
| Web Embed |
Experimental — confirm with platform operator before production |
Validate
- Portal: roles active; channel status connected or explicitly not required (UI-only)
- Provider admin consoles show approved app where applicable
- Pilot user in role reaches Assistant without seeing other roles' Assistants
- Integrator sign-off on technical probe
Limits
Microsoft and Slack approval workflows depend on tenant policy — automation may still require human approval in regulated tenants.
Exact portal labels and activation screens vary by platform version.
Common mistakes
| Mistake |
Fix |
| One Slack or Teams app per Assistant |
Single channel per environment; many Assistants |
| Activating AI before roles are governed |
Complete Operational Trust basics first |
| Skipping identity linking for Slack users |
Require enterprise link before business data |
| Storing client secrets in email or tickets |
Use platform credential store only |