Festivals and sub-fests

The hierarchy

Institution
 └── Festival              SINGLE, or MULTILEVEL
      ├── Levels           MULTILEVEL only: ordered tiers (school → zone → district → state)
      └── Sub-fests        the unit you actually run: Arts, Sports…
           ├── teams, categories, sections, collections, skills
           ├── candidates
           ├── programmes → registrations → results
           ├── venues, judges, schedule
           └── templates, news, gallery, downloads

• A SINGLE festival has one sub-fest, or several independent ones such as Arts and Sports.
• A MULTILEVEL festival has a tree of sub-fests placed on ordered levels, for fests that progress from school to zone to district.

Sub-fests are independent. Each has its own categories, class mappings and programmes. Categories can be cloned from another sub-fest to save setup time.

Creating a festival administrator

In Super Admin → Fests:

1. Create the festival: name, dates, logo, and the public-site slug (and optional subdomain).
2. Choose the access scope:

Scope	Who takes part
TENANT	Only the owning institution
SHARED	The institutions invited in allowed tenants, for an inter-school fest
PUBLIC	Every institution on the platform, including ones added later

3. Issue the organiser logins; see Access.
4. Optionally mark it the default festival, the one served at the bare fest domain.

Sub-fests and levels

In the organiser console, Sub-fests adds the operational units (Arts, Sports, …) with a display order. Levels defines the tiers of a multilevel festival.

Settings

Access → Settings has three tabs:

Tab	Holds
Festival	Profile (name, motto, institution, structure, status, dates), the public website (published, URL path, subdomain), and the participating institutions: a single institution, invited institutions, or open to all
Access	Manager identities, usernames, roles and permissions
Appearance	The look of the console and public site