Design: Improve permission handling when using the bulk deployment functionalities
A discussion should be opened regarding how best to model the permissions around the new bulk deployment functionalities (bulk application deployment and bulk domain deployment).
Leaving both functionalities up to the global NMaaS administrator might result in too much bureaucracy in cases where NMaaS is deployed at a larger university/school. Assigning global administrator permissions to each teacher is also not a flexible approach, since they will be getting error reports and will have access to global NMaaS configuration.
Perhaps a new role with a suitable name (not VLAB-centric such as "teacher") can be created which will have permissions to access both these bulk deployment functionalities and manage user domains.