Changes

***''position'': Describes a combination of one role with one or more titles. For example, the Employee role could include Support Staff, Maintenance Staff, and Security as titles. <Position> nodes within <level> nodes allow the system administrator to give various kinds of Employee different access levels if needed, and also share access levels between multiple roles. A <level> node can have multiple <position> nodes.****'''role_name''': String. The role described by this <position> node.****'''title''': String. A title supported at this access level for the role described in this <position> node. A value of "All" in a <title> node identifies this access level as the default for this role. A <position> node can have multiple <title> nodes.**''whitelist'': A list of users who have administrator rights on the server.***'''username''': String. One user's user ID to grant administrator rights to. A <whitelist> node can contain multiple <username> nodes, although it is recommended to limit the number of whitelisted users.**''blacklist'': A list of users who are banned from the server. These users can still attend meetings which allow guests if they have been given the Guest URL.***'''username''': String. One user's user ID to ban from the server. A <blacklist> node can contain multiple <username> nodes.-**''courseList'': A list of course codes to make available to users creating Lectures.***'''course''': String. A course code. A <courseList> node can contain multiple <course> nodes.