AI Services module
A contextual chatbot, AI-powered insights, mentorship suggestions, and digests — backed by your choice of Anthropic, OpenAI, or Google Gemini, with bring-your-own-model support.
AI Services is the multi-provider AI layer. It adds a chatbot, reachable from the unified messaging/AI panel, that can answer questions about your org's data, plus indexing and retrieval for documents, members, forum posts, and compliance records. Every org can use the platform default provider, bring its own API key, or fall back to keyword search when no provider is available.
Who this module is for
- Members — asking the chatbot questions about events, dues, documents, and the directory
- Officers — quick lookups during meetings and recruitment events
- Org admins — choosing a provider, scoping what the AI can read, monitoring the embedding index
- Platform admins — configuring the platform-wide default provider and re-indexing tenants when models change
What gets enabled
When AI Services is turned on for an org:
- Signed-in users get a Chat with GreekManageAI button inside the unified messaging/AI panel (the floating icon in the bottom-right of every page), which streams answers in real time
- Content embeddings are generated for the data sources the org opts in to, on a nightly schedule and on demand
- Org admins gain AI Services settings — provider selection, model name, an encrypted API key field, content-scope toggles, and an on-demand re-index button
- Onboarding checklists — an admin-authored, step-by-step member checklist rides this module's gate (not AI-generated content); see member checklist and admin authoring
- AI features in other modules — mentorship matching, notification digests, admin reports — light up when their parent modules are also enabled
Bring-your-own-model
Every tenant can run AI on a different provider. The platform supports three:
- Anthropic Claude — chat only; Anthropic does not currently expose an embeddings API, so embedding-backed retrieval falls back to keyword and trigram search when Anthropic is the active provider
- OpenAI — chat plus embeddings (1536-dimension vectors)
- Google Gemini — chat plus embeddings (768-dimension vectors)
The provider that actually answers a question is resolved through a three-step priority chain: platform default first, then the org's own override if it has one, and a platform fallback if both are unavailable. Each level can be marked active or inactive independently.
Content scope
Content-scope toggles decide what the chatbot is allowed to retrieve. All ten ai_scope_* toggles are wired into the org admin panel today, grouped into two sections: Primary content — Member Profiles, Forum Discussions, Compliance Records, Documents, Events, Learning — and System signals & AI workflows — Mentorship Matching, Onboarding Guidance, Notification Digests, Admin Reports. Most are genuine content-retrieval scopes; the one exception is Onboarding Guidance, which acts as a full kill-switch on the onboarding checklist feature's API rather than just narrowing what the chatbot can answer — see content scope for the per-toggle breakdown.
Common workflows
- Members — Using the AI chatbot
- Onboarding checklists — member checklist, admin authoring
- Org admins — provider configuration, content scope, tenant re-indexing
- Platform admins — AI provider configuration runbook for changing the platform-wide default model
- After enabling — AI Services post-enable runbook
What's not in this module today
- Per-response source citations. The chatbot answers in prose; it does not yet attach inline links to the specific record it drew from.
- Thumbs-up / thumbs-down feedback on individual responses. No per-message rating is captured.
Where to go deeper
- AI Services — post-enable runbook
- Using the AI chatbot (members)
- Onboarding checklist (members), onboarding template authoring (org admins)
- Provider configuration, content scope, tenant re-indexing (org admins)
Dependencies
- A configured provider key — platform default, org override, or both
- Storage — for embedding artifacts (platform-managed)
- The modules whose data the AI reads — toggling Documents off, for example, removes documents from answers
Related modules
- Documents — indexed for chatbot retrieval when both are enabled
- Community — forum posts feed the chatbot if the matching content scope is on
- Operations — the chatbot can answer dues, election, and compliance questions
Last verified against v0.65.25 (2026-07-05). Floating chatbot-only widget replaced by the unified messaging+AI panel (same bottom-right icon), v0.65.23 (2026-07-05). Onboarding checklists corrected from an "AI-generated" framing to admin-authored (v0.65.8); removed a stale "no persisted history" claim; corrected content-scope toggle count from "4 wired / 6 pending" to all 10 wired in, and noted the Onboarding toggle's kill-switch behavior.