Every switch, and when to touch it
The administrator decides what the platform is. This guide walks the settings in the order that matters — branding first, then money, then the things you turn on once you have students.
Branding, theme and layout
Settings → Branding takes your dark logo, light logo and favicon. All three are picked from the media library, and the favicon and browser tab title update site-wide the moment you save.
Settings → Theme is the colour palette. Every colour in the product is a design token, so changing the brand colour recolours every tint, badge, chart and glow consistently — you cannot end up with a mismatched screen.
Settings → Appearance chooses the home layout from the available themes, and reorders the sections on it.
Feature switches
Settings → Features is the most important screen in the product. Everything optional is a switch, and a switch that is off ships nothing — no menu item, no empty table, no column in an export.
Quizzes, assignments, live classes, notes, course community, wallet, bundles, ebooks, affiliate marketing, learning paths, academic levels, guardian accounts, leaderboard, calendar, portfolio, announcements centre, AI tools — all of it starts off.
Start smaller than you think
A first-time academy that turns everything on gets a confusing platform and a support load. Turn on what your first cohort actually needs, then add. Switching something on later never loses data.
Payments and commerce
Settings → Payment enables gateways individually. Stripe for cards, PayPal, Fawaterk for the Egyptian market, Tabby and Tamara for buy-now-pay-later in the Gulf, plus manual bank transfer.
Settings → Commerce controls the rest of the money: instalments (how many, minimum price, markup), the student wallet, offline payment instructions with an image, and per-lesson purchase if you sell single lessons.
Bank transfer needs instruction text and ideally a screenshot of your account details. Buyers upload a receipt, you approve or reject with a reason, and they can re-upload.
Buy-now-pay-later gateways need the buyer’s phone number — both providers verify by OTP — so checkout blocks with a clear message if it is missing.
Coupons are managed on their own screen: percentage or fixed, expiry, usage caps.
Content protection and account sharing
Settings → Security holds the four video-protection switches — moving watermark, capture deterrence, hidden URLs and chromeless YouTube — plus the device limits that stop account sharing.
Set a total device cap, and optionally separate caps for mobile and desktop. Leave "evict oldest" on and a student who exceeds the cap simply loses their oldest session instead of being locked out and opening a ticket.
The same screen carries the CAPTCHA choice: Google reCAPTCHA, or the self-hosted TKDS CAPTCHA that keeps visitor data on our infrastructure. It protects login, register, forgot-password, contact and complaints.
Tune protection to your content
A free intro course does not need the watermark. A paid exam-prep library does. Capture deterrence is the one students notice most, so introduce it deliberately rather than switching everything on at once.
Users, roles and permissions
Four roles are seeded: Super Admin, Instructor, Student and Marketer. Beyond those you create sub-admin roles and grant them module by module — orders, analytics, complaints, withdrawals, translations, plugins and the rest.
Permissions are enforced on the server, so a staff member without the orders permission cannot reach order data even if they know the URL.
Settings → Security also sets the instructor sign-up policy: open (auto-approve), review (each application waits in a queue with its CV attached), or closed.
Catalogue and content
Categories support parent and child, which is what drives the navbar mega-dropdown and the catalogue filters. Levels, when enabled, are your own labels — Grade 1–12, A1–C2, Year 1–4 — not something we impose.
Admins can create and edit courses directly, including the full curriculum, and can enrol a student manually onto any course.
Bundles, Ebooks, Learning paths, CMS pages and Blog each have their own screen and each is behind its own switch.
Orders, enrolments and finance
Orders is every purchase with its payment status, and — for bank transfers — the uploaded receipt with approve and reject actions.
Enrolments is the transaction view: which student, which course, and the source — admin, purchase, free, membership or gift. Searchable, and you can enrol a student from here.
Withdrawals is the instructor payout queue. Finance reconciles what was earned, what is owed and what has been paid.
Languages and translations
Arabic and English ship complete. Languages lets you add another, set its direction, and activate it. Translations is the editor for every string in the interface, with a search and a "translate missing" helper.
Content your team enters — course titles, page bodies, blog posts — is translatable per language too, so an Arabic visitor sees Arabic course names rather than English ones.
Email, notifications and announcements
Settings → SMTP configures your mail server and sends a test message. Nothing email-related works until this is set, deliberately — we would rather send nothing than send from a broken address.
The notification matrix decides, per event, whether students get an in-app notification, an email, or both. The email templates themselves are editable.
Announcements centre, when enabled, targets a segment and schedules a message, and shows you who read it.
Analytics and SEO
Analytics gives you monthly and annual recurring revenue, churn, lifetime value, a six-month revenue series, and per-course and per-instructor breakdowns. Every table exports to CSV, and course and instructor names link through to their own analysis page.
Settings → SEO holds site meta, sitemap generation and the tracking tags — GA4, Google Tag Manager, Meta Pixel and custom snippets. None of them are injected until you add them.
Updates and support tooling
Updates shows the current version, lists available releases and applies them, and carries two maintenance buttons: sync translation keys, and auto-translate any extra languages you have added.
Support is the ticket desk your staff answers from — two-way threads with your students, with status and internal notes.
Complaints is the separate footer channel for anyone, signed-in or not, with its own review workflow.
Setting up a new academy?
Onboarding help is included with every paid plan — we will do this walkthrough with you.