Uploaded image for project: 'DSpace'
  1. DSpace
  2. DS-880

Better documentation for permissions

    Details

    • Type: Documentation
    • Status: Accepted / Claimed (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2, 1.7.0, 1.7.1, 1.8.0
    • Fix Version/s: None
    • Component/s: Documentation
    • Labels:
      None
    • Attachments:
      0
    • Comments:
      6
    • Documentation Status:
      Needed

      Description

      Questions:
      How are permissions inherited from community->sub community->collection->item->bitstream
      Both from the perspective of how permissions stacks effect
      and how do permissions for parents affect default permissions for children if at all?

      What does read/write/add/remove/admin mean at each level?
      Can I list items in a collection I don't have read access to?
      Can I see sub communities of a community I don't have read access to?
      What does it mean to be able to add or write to a collection?

      Are there tricks for bulk updating security policies for items, communities, collections, bitstreams, etc.

      Could some of this be made clearer by hiding nonrelevant permissions at some levels?

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                bram Bram Luyten (Atmire)
                Reporter:
                ablemann Alex Lemann
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: