Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-33969

Strengthening group permissions features on Forums tool

    Details

    • Type: Feature Request
    • Status: RESOLVED
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 19.0
    • Fix Version/s: 19.0
    • Component/s: Forums Tool
    • Labels:
      None
    • Conversion Script Required:
      Yes
    • Test Plan:
      Hide

      Test plan configuration
      1 Configure on sakai.properties msgcntr.rolesnone settings (exclude Coordinator roles), i.e.:

      msgcntr.rolesnone.count = 4
      msgcntr.rolesnone.1 = Teaching Assistant
      msgcntr.rolesnone.2 = Instructor
      msgcntr.rolesnone.3 = Student
      msgcntr.rolesnone.4 = access

      2 Configure site, roles, groups, membership...

      For example, create two group/sections with an instructor and a student on each.

      Test plan #1

      3 Create forum for group

       

      4 Check instructor from one group can't see it

       Admin - coordinators view (example with lots of different configurations)

      Instructor section 1 view (can see public and sec1 restricted forums and topics)

      Instructor section 2 view (can see public and sec2 restricted forums and topics)

      Test plan #2
      5 Create topic inside that forum and check again

      Test plan #3
      6 Create a 'public' forum and create a group restricted topic on it

      Test plan #4
      7 Edit any of the restricted forums or topics and check group permissions can't be modified

      8 Check visibility restrictions are kept like before editing

      Test plan #5
      9 Test everything with other roles: student, coordinator...

      Student view

      Show
      Test plan configuration 1 Configure on sakai.properties msgcntr.rolesnone  settings (exclude Coordinator roles), i.e.: msgcntr.rolesnone.count = 4 msgcntr.rolesnone.1 = Teaching Assistant msgcntr.rolesnone.2 = Instructor msgcntr.rolesnone.3 = Student msgcntr.rolesnone.4 = access 2 Configure site, roles, groups, membership... For example, create two group/sections with an instructor and a student on each. Test plan #1 3 Create forum for group   4 Check instructor from one group can't see it   Admin - coordinators view (example with lots of different configurations) Instructor section 1 view (can see public and sec1 restricted forums and topics) Instructor section 2 view   (can see public and sec2 restricted forums and topics) Test plan #2 5 Create topic inside that forum and check again Test plan #3 6 Create a 'public' forum and create a group restricted topic on it Test plan #4 7 Edit any of the restricted forums or topics and check group permissions can't be modified 8 Check visibility restrictions are kept like before editing Test plan #5 9 Test everything with other roles: student, coordinator... Student view

      Description

      Forums uses its own permissions and roles, making it hard to work with groups/sections like other Sakai tools do. There were cases where a teacher modified and deleted forums from a section that was not his. Also, it's important to highlight the fact that some checks were previously done against the "site.upd" permission, which made the groups visibility restrictions harder.

      In order to make the group awareness stronger while keeping with the current Forums model design, we have implemented these features:

      • Allow group restriction for forums, the way it was allowed for topics (see image-2018-03-01-11-24-05-349.png). This option will create one different forum for any of the selected groups, making it only visible for the group members.
      • Just as a reminder, the msgcntr.rolesnone property defines which roles should have NONE permission on those group restricted elements. It should be configured for every role, except Coordinators (those who should see elements from all the groups).
      • Override that feature to allow instructors from a group to create/modify/delete topics on a restricted forum. Previously all the roles from a group acted as contributors.
      • Restrict permission edition for forums or topics created that way: to keep consistency, users won't be able to change the group assigned to a forum/topic.

      Summary:

      Before the fix: instructors could see everything, might delete forums they should not access.
      After the fix: admin / coordinators will see everything, instructors will only see forums/topics assigned to groups they belong to.

        Gliffy Diagrams

          Attachments

          1. Admin Forums1.png
            Admin Forums1.png
            20 kB
          2. ForumsAdmin2.png
            ForumsAdmin2.png
            16 kB
          3. ForumsInstructor1.png
            ForumsInstructor1.png
            18 kB
          4. ForumsInstructor2.png
            ForumsInstructor2.png
            15 kB
          5. image-2018-03-01-11-24-05-349.png
            image-2018-03-01-11-24-05-349.png
            29 kB
          6. image-2018-03-14-13-07-15-485.png
            image-2018-03-14-13-07-15-485.png
            13 kB
          7. image-2018-03-14-13-07-27-943.png
            image-2018-03-14-13-07-27-943.png
            13 kB
          8. image-2018-03-14-13-07-36-216.png
            image-2018-03-14-13-07-36-216.png
            26 kB
          9. image-2018-03-14-13-10-25-282.png
            image-2018-03-14-13-10-25-282.png
            29 kB
          10. image-2018-03-14-13-11-25-139.png
            image-2018-03-14-13-11-25-139.png
            44 kB
          11. image-2018-03-14-13-11-54-232.png
            image-2018-03-14-13-11-54-232.png
            49 kB
          12. image-2018-03-14-13-13-28-615.png
            image-2018-03-14-13-13-28-615.png
            44 kB

            Issue Links

              Activity

                People

                • Assignee:
                  bergarvi Bernardo Garcia Vila
                  Reporter:
                  bergarvi Bernardo Garcia Vila
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  6 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Git Source Code