Skip to content

Conversation

@peterbjohnson
Copy link
Member

  • User access added
  • Removed yarn files
  • Clarified moderator role wording following review
  • Significant re-write admin user_access.md

@peterbjohnson peterbjohnson mentioned this pull request Feb 9, 2026
Copy link
Contributor

@jarkabaker jarkabaker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks — this makes sense overall.

I added one minor comment suggesting a small clarification about global tags and tutor access, but otherwise I am happy to approve.


Personal tutor is listed in the ADMIN panel with other teacher roles, but it is an independent access mechanism derived from student–tutor relationships (tutor access is not a teacher role).

Permissions for personal tutor always includes `View student data`. Other permissions are controlled by ADMIN users and can be enabled or disabled. Whatever permissions are applied, apply to all personal tutors - there is only one configuration of personal tutors.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small clarification suggestion: it might be worth noting here that View student data for tutors is scoped to their tutor group only, and is not the same as teacher View student data (which applies to all students).

This is explained later, but mentioning it here could avoid confusion when reading this section in isolation.


Moderator features require a TEACHER role to include the `Moderate student submissions` permission. TEACHER roles with these permissions cannot be assigned by other TEACHERs (including OWNERs), but can only be assigned by an ADMIN.

Moderators have privileged access to staff-specific comments on MEQ, and this privilege is above that of a module owner. Details available in [../student/MEQ#access-to-meq-data](../../../student/MEQ/#access-to-meq-data). No newline at end of file
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One clarification point: we currently also have custom teacher roles with owner-like names (e.g. “Owner-moderator”), which are not the fixed OWNER role type.

In this sentence, “module owner” seems to refer specifically to the fixed OWNER role. It may be worth making that explicit to avoid confusion with owner-named custom roles.

@@ -0,0 +1,5 @@
Students can be allocated a module tag, which only applies within the relevant module; and/or a global tag, which applies across all modules.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small clarification suggestion:
since global tags are used to define tutor groups and tutor access, it may help readers if this is stated explicitly here, e.g.

“Global tags are used to group students for tutor access.”

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants