Domain level permissions are at a lower level than system level permissions, but are at a higher level than course level permissions and item level permissions. Domain permissions are based on the scope of a domain and around the actions that can be taken.
The scope of a domain is how a domain is organized in terms of the campuses, schools, and departments that it can control. These three factors are mixed and matched to create an appropriate domain for an individual or group of individuals.
Here are four typical examples regarding domain scope:
- Department Chair: will be in a domain that has control strictly over that department.
- Dean: will be in a domain that controls all departments and campuses in their school.
- Provost: will be in a domain that controls all schools, departments, and campuses.
- Site Director: will be in a domain that has control over all departments and schools that are strictly on his/her campus.
The actions cover the permissions available over the domain. They include:
- Administer Courses: If you have permission to administer courses, you have "full" access to all courses within the domain. This means you can see and edit all syllabus content, assign group permissions, modify course settings, and report upon the course. Administer courses does NOT however mean the user can audit the given course as editing and auditing are purposefully separated. You will need to grant audit course permission if you also want the user to be able to audit courses within the domain.
- Audit Courses: If you have permission to audit courses, you can view all syllabi in your domain and update the audit status and trail for these syllabi. It also means you will receive an email if users select the notify auditors option when adding to the audit trail. To learn more about auditing, click here.
- Report on Courses: If you have permission to report on courses, you can view all syllabus content within your domain. This permission is strictly view only.