Quick start

App settings: entry and layers

How each role opens settings, and how personal preferences differ from organization configuration.

startsharedsettings

Audience: Students / teachers / Organization admins / academic admins · Applies to: Same for SaaS and private deploy

Goal: Find the settings entry, and tell apart personal settings vs organization backend configuration.

For preference details, see App settings: preferences.

Two layers of settings

LayerWho changes itTypical content
Personal settings (preferences)The signed-in userAppearance, language & display, practice experience, Notifications (in-app / email), data & privacy (incl. notification retention), etc.
Organization / admin configurationOrganization admins only (and the platform side)Practice policy, branding & domains, import, Plan & usage, Manage team, etc.

Also see Classes and teachers, Manage team: add academic admins, Branding and domains, Trial expiration and formal service.

Where to open

RoleEntry
StudentMain nav MeSettings
TeacherMain nav MeSettings
Organization adminTop-level main nav Settings (config Hub with personal prefs and org route cards); profile and notification lists also under Me
Academic adminMain nav MeSettings (personal prefs / data & privacy personal items; no org-level policy / plan / branding)

Organization admin: top-level Settings = config Hub

After opening Settings, common route cards / groups (copy follows the UI):

EntryWhat you can do
Organization & intakeClass / teacher / student directory, Manage team
Plan & usageTrial activation, plan and billing usage
ImportImport/export and integration batch logs
LogsConfig changes, system errors, login events
Advanced settingsBranding, domains, email
About the platformPlatform capabilities and this instance
Speaking & exams (in-page group)Practice policy, language packs, Voice identity switch
Workbench preferences (in-page group)Appearance, language & display, Notifications, and other personal items
Ops & data (in-page group)Notification retention, storage cache, org data export / cleanup, etc.

Mental model: do work on Home → communicate in Messages → open Settings when you need to configure the system → use Me for profile and notifications. It is normal that academic admin accounts do not see the org-level cards above, but they can still change personal notifications and retention under Me → Settings.

Browser, PWA, and native App share the same personal settings items once opened. See Devices and access.

What each role can see

SettingStudentTeacherOrganization adminAcademic admin
Appearance
Language & display (incl. idle logout)
Practice config / practice experience
Class practice settings
Notifications (in-app / email)
Notification retention (data & privacy)
Data export / cleanupPersonalPersonalOrganization
Organization & intake / Plan / Import / Logs / Branding✓ (Settings Hub)
Speaking & exams (org policy)

Org-level practice policy and plans are visible only to Organization admins. It is normal that academic admins cannot find Plan & usage. For academic admins, Data & privacy is mostly notification retention and local cache—no org export / cleanup.

SaaS vs private

  • Settings items and how you operate them are the same.
  • Differences are mainly access URL, hosting, and commercial terms.
  • Private domains and certificates: Private deploy.

How to confirm a change worked

  • After switching theme or language, you should see the change on the current page or when you return to Home.
  • If save fails, check network and login state, then retry.

Related

Last updated: Tue Aug 11

This guide applies to the DodoSpeak Help Center.

App settings: entry and layers · DodoSpeak Help Center