Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-85738

AI: Add user access controls at course and activity level

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • 5.1
    • AI
    • 10
    • Team Hedgehogs 2025 Sprint 2.2

      Currently, courses have limited means to control access to AI if it is switched on for the site - they can perform some capability overrides but this is complicated, cumbersome to access and not granular enough. In this issue, we will be implementing settings at the course and activity level, which enable more granular control in a user friendly interface (from within the existing settings pages teachers are already familiar with).

      User stories

      1. As a teacher, I want the ability to turn AI tooling on or off at the course settings level, so it is easy to control access to that tooling in my course, and easy to find the setting.
      2. As a teacher, I want the ability to define which AI actions are available within each activity in my course (or to turn it off completely per activity), to give me granular control over which of my activities have certain AI actions available.

      Requirements

      Please see below for a link to the Figma protoype, which demonstrates how the following requirements should be implemented in the UI.

      1. The course settings page will have a new "AI tools" section, which will contain a setting to turn AI on or off for that course.
      2. Each activity's settings page will have a new "AI tools" section. If AI is turned on in course settings, the activity section will contain a setting to turn AI tools on/off for that activity, and if turned on for the activity, each AI action type will be listed and also be able to be turned on/off for that specific activity.
      3. The course setting is the main switch for the course's AI availability - if it is on then activities can have AI turned on or off as above. If the course setting is off, then the activities cannot have AI turned on, it will still have an "AI tools" section, but the contents will be a message indicating AI must first be turned on in the course settings, instead of the actual settings.
      4. Existing access measures are still in place. That means:
        1. If AI is not enabled on a site, it cannot be turned on at the course/activity level, and those areas should not display any AI settings. Note: Any values should be retained, so that if it is turned off and on again, previous settings are restored to the courses/activities.
        2. Existing capabilities should be honoured - for example if a student does not have the capability to use AI but a teacher does, then even if an AI action is enabled for an activity, only the teacher should have access to it (and the student should not see it at all).
      5. All settings should be on by default (course, activity, all actions in activity) for new and existing sites. This retains existing functionality by default, since other requirements mean this only really makes AI available if it is turned on at the site level.
      6. When the course level setting has AI switched off, we must retain all activity level settings (though they will have no effect), so that if AI tools are re-enabled on the course later, the existing configurations are still set and do not need to be configured from scratch on each activity.

      The Figma prototype for this work demonstrates the above requirements and initial language strings required for the various states. The prototype flow is as follows:

      1. Initial state: AI is enabled on the site but turned off in the course.
      2. Visit activity in the course, expanding the AI tools section of settings advises you that AI must be turned on in the course to access the activity level settings.
      3. Navigate to the course settings, and turn AI tools on for the course.
      4. Return to the activity's settings, where the AI tools settings are now available, AI is turned on, and all AI actions are turned on for that activity.

      Out of scope

      1. Any level of granularity not specified above.
      2. Any new pages. All UI changes/additions here are within existing settings pages.
      3. Bulk actions - this will be added as a follow up, and will make it possible to configure activities with the same AI settings simultaneously (for example, you could tick all quizzes and assignments and turn AI off, but turn it on with specific actions for other activities).

            Unassigned Unassigned
            michaelh Michael Hawkins
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 hour, 14 minutes
                1h 14m

                  Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.