What specific challenge or problem does this idea solve? |
Our primary year-long season requires global settings to be configured in a specific way, which prevents us from properly configuring more conventional seasons. Season-level settings would allow for more flexible tuition and registration options, ensuring that configurations for one program do not hinder the behavior of others. |
How should this work? |
We need the ability to manage payment scenarios at the season level rather than being restricted by global parameters. Specific settings found in Magic > Online Registration such as how Tuition is collected at the time of registration, could be implemented at the Season level. For example, I may have one season that we wish to Collect full Tuition at the time of registration (full payment being required), I have other seasons where we collect a deposit at time of registraiton and the remaining Tuition is added to the balance instead. |
Who will benefit (Admins, Staff, Students)? |
Admins benefit because individual season settings allow for clearer messaging and implementation, reducing the need to follow up on incorrect registrations. This flexibility allows the studio to offer various payment structures, such as multi-month tuition for year-long programs, deposit/balance structures for summer programs, or "paid in full" requirements for short workshops or auditions. Students benefit from more flexible and affordable payment options tailored to each program. |
How will this change impact your daily tasks or overall experience? |
This change would significantly reduce administrative overhead by eliminating the need to manually manage registration issues caused by current global configuration limitations. Tailoring settings to the global level would also provide a more cohesive user experience |