Master Data — Overview
Master Data is the identity + configuration foundation read by other domains: Enterprise, BusinessUnit, Org/Site, Account, Account Holder, Attendee, Program/Term/TPS/Product, and image/profile assets.
If Booking/Subscription/Finance are the business flows, Master Data is the terrain map: who belongs to which organization, which sites are active, which programs are open in which term, and which attendee/account is used in a flow.
Quick model
What Master Data covers
| Area | One line |
|---|---|
| Enterprise / BU / Org | Organization scope, site, service area, custom URL, and data boundary. |
| Account / Account Holder | Family/customer account and representative contact. |
| Attendee | Booked child/participant with profile, measurements, requirements, and product config. |
| Requirement customization | School Year/Level/Swimming Competency/height/weight displayed per BU-level customization. |
| Subscription Config | Sys-admin (SuperAdmin BU) assigns Subscription + ProductSet to attendee. |
| Enrollment customization | CustomConsent1..3 and consent fields configured at BU level on enrollment/profile forms. |
| Program structure | Term, program category, program, TPS, term product/session; capacity from TermProgramSetCapacity. |
| Site/program links | Which site opens which program (OrgProgramCategory), which categories/rules are available. |
| Staff links | Employee/OrgEmployee auto-link new staff to active sites; archived are excluded. |
| Images/profile assets | Avatar/profile image/system image and crop policy. |
Read in order
Related
- Booking uses term/product/attendee/account to create orders.
- Subscription uses program/term/enrollment context.
- Finance uses account/attendee/BU/org on invoices and projections.
- Foundation describes common aggregate/ownership.