Platform admin guide to activate role-based Assistants and connect communication channels (Teams, Slack, Copilot, ChatGPT, Web Embed, 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)
Where it happens
- Controller portal — activate AI for roles, view which channels are connected
- Microsoft Teams admin center or Slack app management — approve or upload apps when the provider requires it
- Website or portal owner — deploy Web Embed script when used
Integrators run technical deploy and credential configuration on the Deliver assistant channels guide after you confirm role activation goals.
Steps
- Review roles ready for AI — identify which business roles should expose Assistants (for example Sales Manager with twelve users).
- Activate AI for each selected role — confirm scope, approvals, and evidence expectations with business owners.
- Choose channels — AI Fabrix UI only, or additionally Teams, Slack, Copilot, ChatGPT, or Web Embed per adoption plan.
- Connect each external channel once — not one app per Assistant. Set the customer-visible channel name (for example company or program branding).
- Complete provider approval when prompted — Microsoft tenant admin for Teams or Copilot; Slack workspace admin for Slack; workspace admin for ChatGPT connectors.
- Confirm secure configuration — credentials stored in the platform vault; no secrets in emailed install packages or chat.
- Request integrator verification — integrator confirms inbound validation, identity mapping, and tenant boundary checks (see integrator guide).
- Pilot with real users — users with the active role should see only Assistants they are entitled to.
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 (for audit) |
Channel-specific admin notes
| Channel | Admin focus |
|---|---|
| AI Fabrix UI | No external app; activate roles only |
| 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 |
| Web Embed | Allowed origins and CSP; anonymous mode only for public, non-business content |
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 (documented outside this checklist)
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 |