Options
Permission inheritance
mmcguire
Registered Users Posts: 9 Beginner grinner
Now that we have multiple levels of hierarchy for organization can we get permission inheritance fixed? Each level in the hierarchy should be able to have its own permissions or inherent the parent object's permissions. Here is an example:
Site Homepage (Public)
--> Family Folder (Unlisted)
----> Event 1 album (Public)
----> Event 2 album (Public)
--> Wedding Folder (public)
----> Wedding 1 album (Public)
----> Wedding 2 album (Public)
Currently the wedding logic above works fine, but the family logic does not. If the family folder is unlisted then the event 1 and event 2 galleries must be unlisted or private. We should be able to set the event albums to public. This way we can hand out the URL of the family folder and people can browse the galleries/folders under that hierarchy level. As it stands now the event albums are unlisted so even if you have the URL for the family folder you can not see any albums as a guest.
Permission inheritance should work similar to a filesystem.
Site Homepage (Public)
--> Family Folder (Unlisted)
----> Event 1 album (Public)
----> Event 2 album (Public)
--> Wedding Folder (public)
----> Wedding 1 album (Public)
----> Wedding 2 album (Public)
Currently the wedding logic above works fine, but the family logic does not. If the family folder is unlisted then the event 1 and event 2 galleries must be unlisted or private. We should be able to set the event albums to public. This way we can hand out the URL of the family folder and people can browse the galleries/folders under that hierarchy level. As it stands now the event albums are unlisted so even if you have the URL for the family folder you can not see any albums as a guest.
Permission inheritance should work similar to a filesystem.
0