Skip to main content

School

Purpose​

A School is the primary business entity within Chilarai.

A School represents an educational institution that operates independently within the platform and manages its own academic, administrative, financial, and operational activities.

All business operations within Chilarai are performed in the context of a School.

Examples include:

  • Green Valley School
  • Don Bosco School
  • Delhi Public School
  • Little Flower School

Business Context​

A School represents the customer of the platform.

A School is responsible for managing:

  • Students
  • Teachers
  • Staff
  • Academic Years
  • Classes
  • Sections
  • Admissions
  • Attendance
  • Fee Management
  • Reporting

When a customer is onboarded, a School is created inside a Tenant that provides the identity, isolation, and subscription boundary. The MVP creates one School per Tenant while the durable model permits multiple Schools.

Relationships​

School to Tenant​

  • One School is associated with exactly one Tenant.
  • One Tenant contains one or more Schools.

School to Users​

  • A School contains many Users through School Memberships.
  • Users may belong to multiple Schools.

School to Academic Years​

  • A School contains multiple Academic Years.
  • Only one Academic Year may be active at a time.

School to Students​

  • A School contains many Students.

School to Staff​

  • A School contains many Staff Members.

Key Design Decisions​

School is the Primary Business Entity​

The School represents:

  • Branding
  • Academic Operations
  • Reporting

All business workflows are performed within the context of a School.

Campus Support​

Multi-campus support is intentionally excluded from the initial version.

A School is treated as a single operational unit.

If future requirements emerge, a Campus entity may be introduced without changing the School model.

Board Support​

Board information is configurable metadata.

Examples:

  • CBSE
  • ICSE
  • State Board
  • IB
  • Cambridge

The platform should not contain board-specific logic within the core domain model.

Branding​

Branding belongs to the School.

Branding may include:

  • Logo
  • Primary Color
  • Secondary Color
  • Website
  • Email Templates

Branding configuration applies only to the associated School.

Subscription​

Subscription and licensing belong to the Tenant.

A Tenant subscription supplies the entitlements used by its Schools. The MVP enforces a one-School entitlement through application logic.

School Administration​

Multiple School Administrators are supported.

School administration is implemented through membership-based role assignments.

A School does not have a mandatory single owner.

Attributes​

Identity​

  • SchoolId
  • SchoolCode
  • SchoolName
  • LegalName

Contact Information​

  • PrimaryContactName
  • PrimaryContactEmail
  • PrimaryContactPhone
  • SchoolEmail
  • SchoolPhone
  • Website

Address​

  • AddressLine1
  • AddressLine2
  • City
  • District
  • State
  • Country
  • PostalCode

Academic Information​

  • Board
  • EstablishedYear

Branding​

  • LogoUrl
  • PrimaryColor
  • SecondaryColor

Status​

  • Status

Possible values:

  • Active
  • Inactive
  • Suspended
  • Archived

Audit​

  • CreatedAt
  • CreatedBy
  • UpdatedAt
  • UpdatedBy

Lifecycle​

Created​

School has been onboarded but is not yet active.

Active​

School is fully operational within the platform.

Inactive​

School is temporarily inactive but not suspended.

Suspended​

Access to the School is restricted.

Archived​

School is no longer operational but historical data is retained.

Exclusions​

The following concepts are intentionally excluded from the School entity:

  • StudentCount
  • TeacherCount
  • CurrentAcademicYear
  • AttendanceMetrics
  • FeeMetrics

These are derived values and should not be stored directly on the School entity.

Future Considerations​

The following capabilities may be introduced later:

  • Multi-campus support
  • School groups and federations
  • Board-specific workflows
  • Advanced branding capabilities
  • Region-specific regulatory configuration

These capabilities are intentionally deferred to maintain a simple and flexible core model.

Summary​

Core decisions:

  • School is the primary business entity.
  • School and Tenant have a 1:1 relationship.
  • Multi-campus support is not included in V1.
  • Board is configurable metadata.
  • Branding belongs to the School.
  • Subscription belongs to the School.
  • Multiple School Administrators are supported.
  • Users may belong to multiple Schools.
  • A School manages all academic and operational workflows.