From: alex b. <en...@tu...> - 2001-06-30 23:29:00
|
> Users can create directories if they want, from within the browser. > > We have different kinds of users - administrators, and users, for example. > > Everybody can see the "object permissions" page, and see what the permissions > are for an object they'd like to download. > > But, the owner of the object (who uploaded it) and administrators get > additional functionality on this "object permissions" page - they can modify > the permission set as well as view it. (so an extra button automagically > appears, and instead of listing the permissions, checkboxes are displayed) Right, but wouldn't that mean you would want to have a module on that page that only displays if the user owns the file? That isn't a function of perm. > Additionally, the administrator should have a UI whereby he/she can grant > administrative priveledges to the "object permissions" page. So far, so good. > > So, we have: > 1) permissions to the page ("object permissions") > 2) permissions to portions of the page (set permissions vs view permissions) Sort of, I think this is a function of the module, not the perms system. Though I can imagine a module permissions system. > 3) permissions to the managed object (the things the site manages) > 4) of at least two distinct types (files uploaded, directories) > 5) A means for administrators to grant permissions to other users to the > "object permissions" page. (and presumably other pages as well) > > Does this paint a scenario that makes the needs clear? I can think of several > potential applications where this type of fairly advanced permissions > structure might apply. |