FAQ: DodoSpeak Oral
How Oral differs from the teaching site, how Oral Console’s four identities sign up and sign in, and how the two embed methods and scores work.
Audience: buyers / integrators / Oral Console users
What is DodoSpeak Oral? Is it the same as Oral Console?
DodoSpeak Oral is an Embedded AI Speaking Module: practice / exams inside your own system. Oral Console is only the trial and comparison console, not the product name. See What is DodoSpeak Oral.
Is Oral the same as the DodoSpeak App?
No. The App is the full teaching product (student / teacher / organization). Oral is speaking capability you embed in your own system. See What is DodoSpeak Oral.
Is private deploy a private edition of Oral?
No. Private deploy is still the full teaching product, installed in the customer environment. Oral is capability embed. See Choose Oral, SaaS, or private deploy.
Can we iframe the organization admin console?
No. Oral embeds practice / tasks / History / exams, not the teaching back office.
How do I sign in to Oral Console?
On the DodoSpeak website, open Start Oral Console trial, register, and verify email (do not use the SaaS teaching trial form; the form includes expected learner scale). Then open Oral Console sign-in (this page no longer registers). The sign-in page does not pick a role; you enter as Manager. During trial, switch Learner / Publisher / Developer in the header. After production + sign-in mint, learners and publishers cannot sign in to the Console. Do not ask anyone for shared demo accounts. See How to use Oral Console.
How many identities does Oral Console have? Which is the default?
Four: Learner, Publisher, Manager, Developer. The sign-in page does not pick a role; you enter as Manager. During trial, switch in the header — no extra accounts. Console Manager is not the App Organization login (teaching back office). How-tos: Learner: start speaking, Publisher: publish tasks, Manager: settings hub, billing, and roster, Developer: how to embed.
Where are roster and billing? Still in the sidebar?
Not as primary sidebar items. Manager primary nav is Home / Notifications / Usage / Settings / Me. Roster, groups, team, Plans & billing, invoices, Organization profile, and login logs live on Settings organization-ops cards. Usage stays primary. See Manager: settings hub, billing, and roster.
Why can’t learners sign in to the Console after production mint?
Sign-in mint production entry is school-system login plus a backend short-lived embed token. Console roster cards are no longer issued. After mint lock: learners and publishers enter from the school system; the Console stays for organization ops and developer integration; roster and groups are read-only (delete still allowed). Trial and production + page widget can still sign in learners / publishers on the Console. See Two formal embed methods.
Can we change embed method after production? What if we need both?
Trial can switch on this organization account. Production locks it; you cannot self-serve a change. If the same school needs both widget and mint: open a second Oral organization account and run them independently (usage, keys, and identity stay separate). Do not describe this as hot-switching two methods inside one production tenant. Checklist: What to prepare before you start.
Can a showcase / shared demo account register a credit card?
No. A showcase shop is a shared internal environment and cannot register a card or subscribe. To try Plans & billing, self-serve an isolated trial tenant on the website (one sandbox per person). The UI shows a showcase restriction.
How do Organization profile, Plans & billing, and Me differ?
Organization profile (a settings-hub card) only edits display name, target language, and embed method. Learner roster is a separate card. Plans & billing handles cards, subscriptions, and invoices. Me handles the account and change password (dialog). The last two show a read-only org preview. See Manager: settings hub, billing, and roster.
What does Usage show?
Oral Console Usage shows the tenant pool and personal quota as Usage time (minutes), not turn count. Billing meaning: Minute pool billing.
Is the page widget unofficial or unstable?
No. Page widget and sign-in mint are both formal embeds. Speaking capability, per-person features, and price are the same. The difference is identity: widget issues a learner code in Console (identify before speaking); mint is one request next to your login. Writing back to your LMS gradebook is simpler with mint. See Two formal embeds: page widget and sign-in mint.
How do we get exam scores? Where do learners see History?
In production, learners open the report surface inside your product (same learner identity). Scores are confirmed by your backend via API / webhook. Both widget and mint can look up a person on Oral; writing back by LMS login id fits mint better. See How to get exam scores and view records.
Can we change embed colors and corner radius?
Yes. How to embed Preview can tune the theme and keep the snippet in sync. Production uses theme fields on OralEmbed.mount. That is appearance only — it does not replace learner identity. See How to embed in your system.
Why “publisher” instead of teacher / assigner?
The Console only demos “who sends tasks to learners.” Production job titles are yours. The UI label is Publisher.
We are on Lite. Why is Exams still visible?
All four surfaces stay visible; the API rejects when the plan does not include that surface. Do not hide buttons by plan. See Plans, entitlements, and usage.
Can the organization key go in the frontend?
No. Backend only; the browser receives a short-lived embed token. The page widget uses a publishable key, which is not the tenant key. See How to embed in your system.
Will Oral Console’s four roles appear in our production product?
They are not required Oral roles. Your system owns production roles, login, and permissions. Console Manager / Developer / Publisher / Learner are only for integration and trial.