Key takeaways
- Configure school identity, visibility, revenue shares, team, course collaborators, posts, discounts, and promo codes.
Open this area in SubSchool
Directors can configure the school and team. Teachers can view the school and use only the actions permitted by their role.
Step 1. Open School
Click School. Confirm the school name and that your account is the director before changing team, shares, or public settings.

Step 2. Edit identity and visibility
Click Edit. Upload a clear logo, enter the official school name, choose a stable URL slug, and write a public description. Private restricts discovery, Unlisted is reached by direct link, and Public appears in discovery. Default course/tutoring school-share percentages determine the school portion unless a teacher-specific override exists; values are 0–100 and should be agreed before sales.

Step 3. Review the team and effective shares
The Teachers section shows membership and role. A director may set teacher-specific course and tutoring shares, save each row, promote a teacher to director, or remove a teacher. Check the resulting school/teacher percentages after saving because the transfer-of-director action changes your own permissions.

Step 4. Assign course collaborators
For each school course choose a member and role. An Author edits and owns content decisions; a Curator supports learners and operations. Add only one agreed role per person/course and remove stale access.

Step 5. Publish school posts
Open Posts, click Create post, and add title, short description, URL slug, cover, and rich-text body. Save as draft while reviewing; publish only when links and media work on the learner-facing school page.

Step 6. Create discounts and promo codes
Open Discounts. Set a percentage from 1 to 99, optional expiry, and all paid school courses or a selected subset. Promo codes additionally require a unique code and activation limit. These discounts affect learner purchases; preview the scope and expiry before creating them.

Sources and methodology
The workflow, labels, validation rules, and resulting states were checked against the live test environment. Screenshots were captured by Playwright at 3840×2160 and reviewed at full resolution.

