Feature Request

The whole point is that you're teaching them, right? Shouldn't they have access to all of the features? You want them making mistakes at school, not once they're out in the real world. Patch especially. If you're not capable of using patch correctly, you're not capable of being a programmer.

Tony's request is valid, because unfortunately not every school is a School for Technical Theater, and sometimes, there is only a Drama Teacher who doesn't know much about technical aspects, and where a ETC Dealer came and commissioned the site, and got it running, and then if someone comes in and changes aspects of the console settings like the patch, then the Drama Teacher and the students might not be able to get the console back to a working state.

I will agree with Andrew though that special access levels is not the best solution here, rather its best to have created a base show file with all of the patch

and maybe general submasters, presets, palettes, snapshots and macros saved, and then build each event from that showfile. Then, if the students mess the showfile up so badly, then you can just open the base showfile and start over.

Its also good to save your specific show files multiple times a day during programming/tech rehearsals so that if a student messes something badly up you can go open a last saved verson of that show to before the mess up point.  

Tony's request is valid, because unfortunately not every school is a School for Technical Theater, and sometimes, there is only a Drama Teacher who doesn't know much about technical aspects, and where a ETC Dealer came and commissioned the site, and got it running, and then if someone comes in and changes aspects of the console settings like the patch, then the Drama Teacher and the students might not be able to get the console back to a working state.

I will agree with Andrew though that special access levels is not the best solution here, rather its best to have created a base show file with all of the patch

and maybe general submasters, presets, palettes, snapshots and macros saved, and then build each event from that showfile. Then, if the students mess the showfile up so badly, then you can just open the base showfile and start over.

Its also good to save your specific show files multiple times a day during programming/tech rehearsals so that if a student messes something badly up you can go open a last saved verson of that show to before the mess up point.