- Access Policies
- Gradebook Policies
- Quota Policy
- System-Wide Announcements Policy
- System-Wide Groups Policy
- Third Party Software Course Management System (CMS) Integrations
All requests for access to the Course Management System (CMS) must be sent to the eLearning Department via a Service Request to the LCC Help Desk.
Gradebook Policies (Academic Senate, Spring 2016)
D2L is provided to all faculty to use for the purpose of recording grades electronically. Although all faculty are expected and encouraged to use D2L, the following criteria must be satisfied by all faculty, whether they use the D2L gradebook or any other electronic gradebook system.
A 500 MegaByte (MB) quota is imposed on all Course Management System (CMS) course sites in order to maintain the highest level of functionality. As a result of this policy:
Once a course exceeds the limit, the Instructor will be notified and/or assisted by a member of the eLearning staff to develop and execute a plan that fits the needs of the course.
System-Wide Groups Policy
Group Sites in the Course Management System (CMS) are to be used for communicating with and distributing content and information to Students and Instructors related to academic courses. All requests for the creation of Group Sites will be approved by the Director of the eLearning Department.
LCC employees may be added to a Group Sites as Group Editors only if they have completed the assigned Course Management System (CMS) Teaching Online with D2L (Instructor Training).
System-wide Announcements in the Course Management System (CMS) are to communicate critical academic or system-related information to Students and Instructors. All requests to post system-wide Announcements will be approved by the Director of the eLearning Department.
All new third party software CMS integrations must be requested via the Help Desk. Timelines for third party software CMS integrations must be approved by the Director of the eLearning Department. Third party software integrations must be thoroughly tested by the requestor as well as the CMS administrator before being integrated with the CMS production instance.