Documentation Search and AI Support
The Manager console and public Portal expose the same documentation-support entry point. It uses only the public Manager and open-source Web documentation shipped with the current release and lists the actual sources below each result.
Anonymous search, signed-in AI, and plan usage
You can use the default documentation index without signing in. Anonymous searches are protected by trusted-client-IP minute and daily limits; they make no AI call and consume no plan allowance. The UI offers sign-in for full AI support only when administrators have enabled AI and its runtime is ready.
Actual model usage after sign-in is always charged to the current user's personal plan, never to the active organization. If administrators turn AI support off, signed-in users can still use the default index and the entry point is labelled “Search.”
Signed-in AI support allows multiple follow-up turns. A bounded number of recent completed questions and answers helps resolve references such as “this setting” or “the previous step.” Every turn still searches the documentation again; the model cannot answer freely without public-document support. Anonymous index search is stateless source retrieval and has no AI follow-up understanding.
After the first question arrives, the conversation immediately uses a cropped version of that question as its title. When AI is enabled and the first answer succeeds, one additional short model call creates a more concise title; its actual usage is also charged to the personal plan. A title-generation failure never affects the answer and keeps the cropped fallback title.
Retrieval and query rewriting
The service first searches a local BM25 index with the original question. When confidence is low, the platform model rewrites the intent into two to four search queries and the service performs one more retrieval. The model cannot access files, websites, or the index and cannot search indefinitely. If the second retrieval still lacks reliable support, the turn ends explicitly with no documentation match.
Query rewriting and the final answer are separate real model calls, so a low-confidence question can produce two answer-related usage entries. A successful first turn can add one short title call. If rewriting succeeds but the answer call cannot be admitted because allowance was consumed concurrently, the UI reports an actionable reason and the completed rewrite usage remains charged.
If platform AI is temporarily unavailable, support can still return related sources from the default documentation index. The UI shows an explicit fallback notice; this path makes no model call and produces no model usage.
Retention and deletion
Questions, answers, rewrite results, and citation snapshots are retained for 30 days by default. A platform administrator can configure the period from 1 to 365 days. You may delete your own terminal conversations, and the UI asks for confirmation first. If a turn is still being admitted, queued, or generated, cancel it and wait for a terminal state before deleting the conversation.
Long-term usage and service-health statistics do not retain question or answer text. See the Portal Privacy Policy for the exact data sent to the configured model provider.
Boundaries
Documentation support does not inspect account balances, live device state, or private administrator documentation. It cannot connect to a device, call tools, or execute commands. Use the corresponding console page for live account, plan, and device state. If the documentation does not cover a question, the assistant says so and ends the turn instead of guessing or listing unrelated index results.