eJournal works with a wide range of permissions that are grouped into roles. Some well-known roles are Student and Teacher, where, for example, the Student role has the permission to have a collection, and a Teacher role has the permission to grade. Each user holds a single role within a course or programme, but a user's role may vary between different courses or programmes.
Note that some special types of permissions exist, such as the ability to create a programme. These permissions can only be granted by administrators; for an overview, see administrator permissions.
Roles can be configured in the permission manager of the respective course or programme by users with the can edit roles permission.
By default, each course and programme has the roles Teacher, ContentDeveloper, TA, TestStudent, and Student, each with a set of sensible default permissions.
When working with eJournal from your LMS (e.g., Canvas or Brightspace), each user is granted an appropriate role automatically. The exact mapping is configured by your instance administrator here.
Students own a portfolio. Students can structure portfolios in the form of collections, ask for feedback, or place comments.
If you want to see how a student perceives an assignment or course you created, you can put it to the test. This could be beneficial in the case of unpublished assignments.
Teaching Assistants (TA)s are the first tier of supervisory staff, and are somewhat limited in what they can do. By default, TAs can grade, view analytics, and manage individual collections. However, TAs cannot create or make changes to (existing) assignments or course/programme structures.
Content developers can scaffold programme/course and assignment structures and see collections or analytics. However, content developers cannot grade or provide feedback.
Teachers are the key users of a course or programme. Teachers can make structural changes to a programme/course and assignment and have access to all grade and feedback tooling.
Permissions can be assigned to specific roles within the permission manager.
Users with this permission can change high-level course/programme information such as the name, abbreviation, start, and end date of the course, as well as link the course to any programme the user is part of.
Users with this permission can delete a course/programme.
Users with this permission can make changes to existing course/programme roles or add new ones.
Users with this permission can change the role assigned to a user within a course or programme.
If a role is available that has the can edit roles permission, users with this permission can assign themselves that role.
Users with this permission can view all the course/programme users and their role.
Users with this permission can add users to a course/programme.
Users with this permission can remove users from a course/programme.
Users with this permission can create new groups to a course/programme.
Users with this permission can remove groups from a course/programme.
Users with this permission can make changes to course/programme groups, such as its name and its member composition.
Users with this permission can create a new assignment within a course/programme.
Users with this permission can remove an assignment from a course/programme or delete the assignment if no other course is using that assignment.
Assignment deletion is final; any work part of the assignment is also deleted.
Users with this permission can make changes to an assignment and its structure. This governs both the ability to change assignment information such as its name and due date, as well as the ability to change structures within the assignment such as activities, templates, and rubrics.
This permission also governs creating or changing inactivity notifications for an assignment.
Users with this permission can view analytics of their students such as the assignment analytics.
This permission also governs viewing inactivity notifications for an assignment.
Users with this permission can grade collections and entries within the course. This also determines whether the user can see plagiarism reports.
Users with this permission can publish grades.
Users with this permission can view all collections within a course.
Users with this permission can view all collections of users that are part of their own groups.
Incompatible with the permission can view all collections.
Users with this permission can view unpublished assignments.
Users with this permission can view the grade history of an entry or the overall assessment of a collection.
This permission can currently not be granted to students. Making this permission compatible with the Student role is on our radar for the near future.
Users with this permission can interact with collection-related settings.
For group assignments, this would be settings such as the number of group collections, the number of members per group collection, and settings such as the name, image, and member composition of a specific group collection.
Besides group assignment-related settings, this permission also governs whether the user can submit or cancel a collection submission for assessment.
This setting is intended for collection supervision, and is not available to collection owners (can have collection). If you would like to grant these rights to students, see the respective assignment group and submission settings.
Users with this permission can have a collection within an assignment.
This permission is incompatible with permissions such as can grade, as teaching staff is not allowed to have a collection in the same assignment.
Users with this permission can comment on individual collection entries.
Users with this permission can edit the comments of fellow staff. For example, a course coordinator might want to be able to tweak comments placed by their teaching assistants.
Users with this permission can add entries to collections as a teacher.
Users with this permission can manage the requests from students to import content into their collection from another assignment.
These permissions cannot be configured in the course manager. These
permissions can only be acquired based on your LMS credentials, or given to you by an instance administrator.
This is a special type of permission generally only available to administrators of your institution. Users with this permission have access to the administrator panel, which allows for the configuration of settings such as the name of the institute and whether self sign-up is enabled.
Users with this permission have the ability to create a new course.
Users with this permission have the ability to create a new programme.