Authorised QA workspaces and invitation-led client demos have separate assistant controls and limits, with no real account-wallet spending.
Quick answer
An invitation demo can offer optional text AI when Admin enables it for that demo, with up to ten requests per invitation and consent for each question. Existing QA workspaces retain their separate assistant access. Neither uses a real account wallet.
In /demo/client, open AI help if the person arranging your demo enabled it. It is off by default for each invitation. You can always use the ordinary guide and demo controls without AI.
Before each question, choose whether to send that question and minimal fictional context to OpenAI. The context includes your selected demo role, booking counts for that role and supported local navigation options. Previous chat, lesson notes, messages, feedback and contact details are not included automatically. Avoid entering personal or sensitive information. The displayed conversation stays in the page and clears when your demo role or binding changes.
Each invitation has at most ten text AI requests in total, shared across role changes, reconnects and resets. No real account credits are used, but actual provider usage still uses FASS's configured AI budget. A dispatched request can use an allowance even if no reply is delivered. Voice and AI changes to bookings or accounts are unavailable in this separate adapter.
The assistant may offer to open a supported demo tab. You choose whether to accept; existing unsaved-change checks still apply. It cannot open real accounts or guarantee that your problem is fixed. If help is unavailable or the allowance ends, continue with the guide or contact the person arranging your demo.
Existing authorised QA workspaces can enable the assistant separately for a fictional demo school. The server checks the current actor, selected demo school and its setting; selecting a school ID or adding a URL parameter is not permission to use it.
The signed HttpOnly fass_assistant_demo_scope cookie remembers the requested workspace for at most three hours. It is bound to the authenticated actor and authorised demo context, not a general account or school-access grant. Permissions and the setting are checked again on later requests.
School catalogue results and supported school actions remain inside that fictional school. A lesson draft or booking reschedule still needs the exact preview and explicit Confirm change control. The assistant cannot use the demo to modify a real account's name or bio, fetch real personal saved preferences or change another school's records.
Demo allowances are isolated from real account-wallet spending. Actual voice/text provider usage still consumes the configured OpenAI project budget, and normal safety and conversation limits apply. AI consent and explicit microphone start remain required.
A private preview link is different: it enables ordinary assistant access in one browser without supplying a fictional school or extra permissions. A self-service flow that creates a temporary demo account for any public visitor is not currently provided by these features. If you need a demonstration, contact the person arranging your test or FASS support.
Still need help with this article?
Send the article URL and the step that needs more explanation.