Franchise organization tree
Manage branches and academies under headquarters, with room for future area or division layers.
Manage franchise headquarters, branches, academies, classes, and students as one organization hierarchy.
Academy subdomains and role-based permissions support both local autonomy and central control.
SaaS Admin
Headquarters Tenant
Branch/Academy Organization
Class & Student Operations
The initial model starts with SaaS, headquarters, branch, academy, class, and student. Additional organization levels can be inserted later.
Manages shared policies, products, domains, and global operations.
The franchise headquarters becomes the tenant and top-level organization admin.
Represents regional or business-unit level middle organizations.
Each academy operates as a logically isolated management unit.
Classes manage lessons, materials, attendance, progress, and assignments.
Connects students, guardians, enrollment history, and learning records.
The MVP stabilizes organizations, permissions, classes, and students first, then expands payments, buses, and messaging as modules.
Manage branches and academies under headquarters, with room for future area or division layers.
Separate access scopes for SaaS admins, headquarters admins, branch admins, and academy admins.
Designed to support academy-specific addresses such as jongro.hakwon.how.
Align class placement, enrollment, guardian links, attendance, and learning history with operations.
Headquarters sees global metrics while branches and academies view only their own scope.
Implemented for multi-saas-kit patterns with organization hierarchy changes and SaaS module expansion in mind.
hakwon.how is the primary domain. Academy default domains use {academy}.hakwon.how.
Primary service
hakwon.how
Default academy domain
{academy}.hakwon.how
Compatibility domain
hakwon.academy.how
After the landing page, the next steps are SaaS product setup, headquarters tenant, organization tree, and academy subdomains.