Details

    • Similar Issues:
      Show 5 results 

      Description

      Before LPS-32269, only categories and folders would pass on permissions to children categories and folders. After the changes, the following inherit permissions from parents:

      • if a category has a permission, the children (both threads and categories) will also have that permission
      • if a folder has a permission, the children (both file entries and folders) will also have that permission
      • if a wiki node has a permission, the children (wiki pages) will also have that permission
      • if a wiki page has a permission, the children (wiki pages) will also have that permission
      • if a bookmark folder has a permission, the children (bookmark entries and folders) will also have that permission

      We should have a property that allows for our older functionality - no inheritance from parents of different classes.

        Issue Links

          Activity

          Hide
          Randy Zhu added a comment -

          In preparation for Ideation; we are merging New Feature and Improvement tickets into a singular ticket type called “Feature Request”. Additional information to follow soon.

          Show
          Randy Zhu added a comment - In preparation for Ideation; we are merging New Feature and Improvement tickets into a singular ticket type called “Feature Request”. Additional information to follow soon.
          Hide
          Peter Mesotten added a comment -

          Hi Randy,

          I cannot reproduce the fact that when you create a DLFolder (in 6.1 GA2), it will inherit the permissions of the parent DLFolder. Also, the issue you linked to only concerns Message Boards entities, so I don't really understand how this is linked to this issue.

          Show
          Peter Mesotten added a comment - Hi Randy, I cannot reproduce the fact that when you create a DLFolder (in 6.1 GA2), it will inherit the permissions of the parent DLFolder. Also, the issue you linked to only concerns Message Boards entities, so I don't really understand how this is linked to this issue.
          Hide
          Kenneth Chang (Inactive) added a comment - - edited

          Hi Peter,

          If you check LPS-32269 you can see which versions have the fix/improvement by looking under 'Fix Version/s:'. This was fixed after 6.1 GA2.

          Ops! Sorry you couldn't see the comments, I'll leave another on LPS-32269.

          Show
          Kenneth Chang (Inactive) added a comment - - edited Hi Peter, If you check LPS-32269 you can see which versions have the fix/improvement by looking under 'Fix Version/s:'. This was fixed after 6.1 GA2. Ops! Sorry you couldn't see the comments, I'll leave another on LPS-32269 .
          Hide
          Tino Schwarze added a comment -

          Hi all,

          this exact feature totally broke our (intended) setup. OTOH we depend on it.

          We are trying to implement a folder structure in Document Library like this:

          • main folder -> visible to role 1 and 2
          • subfolder group 1 -> visible to role 1
          • subfolder group 2 -> visible to role 2

          Because of (totally invisible) inheritance of permissions, everybody get's access to every folder. There is no way to restrict access to a subfolder (apart from removing the main folder altogether and only use lots of subfolders or creating page-scoped DL portlets).

          Since the default permissions of documents are usually left at Guest-viewable, we still NEED inheritance or every user would have to correctly set permissions on every uploaded document (write permissions unfortunately do not inherit!).

          This behaviour is rather inconsistent IMO.

          A proper solution would make inheritance explicit (remember Windows directory permissions). It would also include the ability to specify default permissions for documents added to a folder.

          Show
          Tino Schwarze added a comment - Hi all, this exact feature totally broke our (intended) setup. OTOH we depend on it. We are trying to implement a folder structure in Document Library like this: main folder -> visible to role 1 and 2 subfolder group 1 -> visible to role 1 subfolder group 2 -> visible to role 2 Because of (totally invisible) inheritance of permissions, everybody get's access to every folder. There is no way to restrict access to a subfolder (apart from removing the main folder altogether and only use lots of subfolders or creating page-scoped DL portlets). Since the default permissions of documents are usually left at Guest-viewable, we still NEED inheritance or every user would have to correctly set permissions on every uploaded document (write permissions unfortunately do not inherit!). This behaviour is rather inconsistent IMO. A proper solution would make inheritance explicit (remember Windows directory permissions). It would also include the ability to specify default permissions for documents added to a folder.
          Hide
          Juan Fernández added a comment -

          Closing as per Kenneth's request

          Show
          Juan Fernández added a comment - Closing as per Kenneth's request

            People

            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Days since last comment:
                1 year, 44 weeks, 3 days ago

                Development

                  Structure Helper Panel