Find the right guide before you get stuck.

New learners create a learner account, finish onboarding, choose a language track, and land in learner home. Returning learners should sign in with the same email so progress and class links stay on one account.

You do not need a second learner account when a teacher later invites you. The same learner account can hold self-serve collections, organisation-linked lessons, and assigned work.

Start with Learner home, then check Classes for linked access and Inbox for due work or follow-up signals.

• Use Classes when a join code or invitation is real.
• Use Learner home for assigned work, recent study, and self-serve collections.
• Use Profile to confirm your account details and current learner setup.

Use the invited email, accept the invitation, and treat expired invitations as an access issue that needs a fresh invite rather than a new account.

Create or open a class, prepare learner access through roster or join-code flow, then assign collections and monitor what needs follow-up in Analytics or Inbox.

Analytics is a shared aggregate view with comparison and intervention tracking. It is not yet a final learner-by-learner reporting system.

• Use Analytics to spot lessons or classes that need attention.
• Use Inbox when you want the next grounded action without scanning every page.
• Escalate organisation setup or platform-wide issues instead of forcing them through teacher pages.

Organisation Admins coordinate staffing, access, learner linkage, and teacher support inside their own organisation. Platform-wide creation, deployment, and release decisions stay outside this role.

Check staff access, invitation state, and learner roster health before assuming a class or content workflow is broken.

If the problem is bigger than one organisation, or depends on platform setup, environment changes, or code repair, pass it to a Platform Admin or engineering contact instead of treating it as an organisation-side workflow.

Platform Admin work is about shared platform setup and support, not one organisation's day-to-day classroom delivery.

The release-readiness page collects current evidence, operational signals, and residual debt. It is not a deployment button or production incident console.

Organisation setup, invitation handling, and content operations are routine product work. Migrations, deployment, secrets, and infrastructure failures are engineering-only escalation paths.

Use password reset before creating a second account. If the email is wrong on an invitation, sign out and continue with the invited email instead.

Check whether the code or invite is still current, whether you are signed in with the right account, and whether the role matches the flow you are trying to enter.

• Learner class invites only work for the invited learner email.
• Teacher access is invitation-led; it is not a public sign-up route.
• Expired invitations need a new invite rather than repeated retries.

Check Classes first for linked access, then Learner home or the teacher workspace for assigned work and follow-up, then Inbox for grounded reminders. If the issue is really about organisation or platform access, escalate it rather than treating it as a lesson bug.

Use a current desktop or tablet browser for the most reliable experience. The installable app shell is supported, but the current product should still be treated as an online-first classroom system.

Cached lesson pages and local learner state can survive on the current device, but fresh shared data, class updates, and server-backed reads still need a connection.

The product keeps learner progress, quiz attempts, and account data tied to the signed-in account. Browser-local lesson analytics is diagnostic and secondary, while shared teacher analytics uses persisted progress and attempt records rather than claiming a wider surveillance model.

Learner home is the steady signed-in destination, with assigned work, organisation-priority content, and self-serve collections kept together. No action is required if you already sign in with the right learner account.

Teacher workflows now keep classes, collections, analytics, organisation operations, and inbox follow-through easier to reopen from one signed-in workspace. Use the role guide if you are unsure which page now owns a task.

Platform operations now include a bounded release-readiness view plus the current content and invite-delivery tooling. Use the platform guide if you need a plain-language reminder of which tasks are routine product operations versus engineering-only work.