SOQ International Academy

Important Points

Platform owners and technical operators complete these post-install checks before opening SOQ International Academy to learners. Actions happen at the configured Admin URL, Contabo / XAMPP environment, and soq.edu.sg for human support.

important screenshot

Live screenshot from the SOQ beauty demo (aiacademy.aiee.dev).

Surfaces, roles and current terminology

SurfaceCurrent navigation terminologyStatus
Feature togglesAdmin → Features / SettingsCore activation flow
Support channelExternal support via soq.edu.sgOps / support
Hosting and environmentRequirements → Installation checklist (Contabo / XAMPP)Core
Admin accessConfigured Admin URL (default /admin)Core
Update readinessDeploy + migrate; see How to UpdateCore

Permissions, settings and activation

  • Confirm hosting meets Requirements before running Installation.
  • Do not publish learner traffic until SMTP/mail and financial basics are verified.
  • Use the configured Admin URL; installations may change the default admin path under Security.
  • Keep DEMO_ONE_CLICK_LOGIN=false on customer production.

Core workflows

Confirm feature activation
  1. Sign in at the configured Admin URL (demo: admin@soq.edu.sg / Demo@1234 after beauty seed).
  2. Open Admin → Features / Settings and enable only the optional features you need.
  3. Contact soq.edu.sg for commercial and support entitlements.
Prepare hosting and install
  1. Confirm PHP, extensions, database, and storage against Requirements (Contabo VPS standard).
  2. Deploy the app with document root on public/, configure .env, run migrate + db:seed — see Installation.
  3. Optional pitch data: php artisan demo:seed beauty (beauty only).
  4. Open Settings → General for site identity and timezone; configure SMTP before mail-dependent flows.
Open the platform safely
  1. Review Security (admin path, captcha) and Financial (currency, tax, gateways) before sales.
  2. Disable Maintenance when content and payment smoke tests pass.
  3. Verify a student can register or sign in and open one course learning path.

Result states

  • Success: Admin URL works, Features toggles stick, mail and checkout basics succeed, public site is not stuck in maintenance.
  • Pending: Hosting not ready, SMTP unfinished, or Features not reviewed.
  • Denied: Staff lack Settings / Features permissions.
  • Error: Install, cache, or environment misconfiguration blocks Admin login — fix hosting and .env first.

Operational notes

  • Treat this page as an operator checklist, not a separate Admin module.
  • Never hardcode a fixed admin prefix in runbooks; always say configured Admin URL.