Permissions allow users to access certain features of a course or project site, depending on their roles, and on the decisions made by the site owner and the system administrator.
Roles are collections of permissions. Some roles allow users to simply access or read content, while other roles allow for advanced changes, such as adding participants, editing the site's content, and changing permissions for other roles.
When you create a site, or when one is created for you, you have the role with the most permissions and the broadest level of access. You can choose (within the limits established by the system administrator) which tools or functions (e.g., Forums, Calendar, Resources) you want the site to have. For many of these tools or functions, you can set permissions that allow or prevent users from seeing or performing certain tasks, depending on their roles.
Roles may vary in name, depending on the application. However, in general, the creator of a project site, or the instructor of a course site, has full permissions, and can add or delete content within a site.
A user who joins an existing site has a more limited role. The permissions of this role allow for interaction in the site (e.g., creating Chat messages), but do not allow for advanced tasks (e.g., uploading files into Resources or creating assignments).
However, each implementation of the application will be different. System administrators can decide during implementation which roles to install, and which permissions these roles will have.
Some things to remember:
The following default roles are available in course and project sites:
Many institutions create custom roles with specific sets of permissions for their local systems. Custom roles must be created by a system administrator using the Realms tool.