![]() Roles without this option can still see past course offerings listed in the My Courses widget if the configuration variable is enabled.The name of the role as it appears in Classlist.Ĭontrols whether the role name appears in Classlist.Ĭontrols whether the role name appears in Seating Chart.Ĭontrols whether users in this role can access inactive courses.Ĭontrols whether users in this role can access course offerings after the end date specified on the Course Offering Information page. When enabled, users with this role are primary facilitators of the course.Ĭontrols whether users in this role can appear on attendance registers.Ĭan have content statistics, feedback, and SCORM reportsĬontrols whether you keep statistics for, give feedback to, and include in SCORM reports for users in this role.Ĭontrols whether users in this role can be assessed in the Discussions tool.Ĭontrols whether statistics are kept for users in this role in the Discussions tool.Ĭontrols whether grades can be assigned to this role.Ĭontrols whether users in this role can self-enroll in groups set up for self-enrollment.Ĭontrols whether users in this role can register in courses.Ĭontrols whether Class Progress information is recorded for users in this role.ĭisplay users enrolled as this role in classlistĬontrols whether users in this role appear in Classlist. When enabled, users in this role automatically have access to all org units beneath the one in which they are enrolled. The description is visible on the Role List page. Role properties terminology General FieldĪ short description of the role. You assign permissions to a user for a specific org unit by enrolling the user in that org unit in a specific role. Cascading roles are normally used for site administration. For example, if you enroll a user in the science department in a cascading role, the user is automatically enrolled in all course templates, course offerings, and groups and sections under that department. If a role is cascading, a user enrolled in any org unit in that role is automatically enrolled in all other org units beneath it. You can create any number of roles for your organization and enroll individual users in different roles for different org units. Assigning permissions to a role dictates what users in that role are able to see and do in the system. You can define custom types to match your organization’s structure, such as consortium, college, community of practice, cohort, etc.Ī role is a mechanism for storing a set of permissions. By default, Brightspace contains org unit types for course offerings, course templates, departments, semesters, and the organization. Org units define the structure of an organization. As a security measure, you can choose to disable locker file sharing for the guest role. For example, you can set the configuration variable that allows locker file sharing in your Brightspace. ![]() When you set role permissions, you are configuring what aspects of that functionality are available to the role. When you set a configuration variable, you are configuring specific functionality in Brightspace. Role permissions are not the same as configuration variables however, the two objects share a relationship in Brightspace. Role permissions versus configuration variables Create, define, change, delete, and copy user roles.Use Roles and Permissions to do any of the following: When a user accesses an org unit, they have access to the features set up for their role in that org unit. You assign permissions to roles and then assign roles to users for specific org units. Permissions correspond to tools in Brightspace and D2L products, for example, the ability to create discussion topics or edit an org unit’s navbar. Use Roles and Permissions to set what functionality is available to different users.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |