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:
The actions cover the functions available to you within the given domain. They include:
Also note that these permissions are additive, flexible, and may layer on top of each other. For example you can be designated a Reporter across all domains, an Auditor for one campus plus three departments, and an Editor of a whole school and all its department.
Additionally, select capabilities are implied with others. For example, if you can Edit content, you can implicitly view it. Similarly if you can Audit content, you can view it. An individual with Administer, Edit, or Audit does not also need Report to pull syllabus reports - this does not include access to CV reports. Becuase CV's are attached to people and not to syllabi, a user must either have Administer or Report access to pull CV reports.
You can add or update a user's domain permissions by going to Admin > Users and searching for the username of the appropriate user. Once you have selected the appropriate user, you will be able to update their domain permissions by selecting the appropriate campus, school, and department information and checking Administer, Edit, Audit, or Report.
Once your comfortable with how domain permissions work, you can learn how to assign Domain Permissions in your system.