Murat Posted December 5, 2013 Report Share Posted December 5, 2013 One of the most requested features for Daminion Server is adding support for multiple shared catalogs. To split different type of content or to separate an access for certain group of users on file (item) level. So to partially cover this demand, we decided to add add a new feature named "Restricted Areas" that allows to limit an access to certain group of items for certain group of users. This is a test name, becauase I don't sure whether it sounds right for native English speakers). I've posted below some possible variants for this term. Any feedback are very welcome! Possible variants are: - Scopes - Zones - Visible Areas - Visibility Scope - Access Zones - Restricted Areas - Access Areas - Access Restrictions Quote Link to comment Share on other sites More sharing options...
rene Posted December 5, 2013 Report Share Posted December 5, 2013 Hey Murat, you could just call it "Permissions". This would than be applied to every User. Like on Website and Windows demands. When the Admin hast access to everything, editors only to certain folders or pathes. That would work for me. Quote Link to comment Share on other sites More sharing options...
Murat Posted December 5, 2013 Author Report Share Posted December 5, 2013 Permissions is too general term. We also have permissions on functionality level (via User Roles). While a term I need to select is for permissions on a file level. Quote Link to comment Share on other sites More sharing options...
rene Posted December 5, 2013 Report Share Posted December 5, 2013 ok, no idea than! Quote Link to comment Share on other sites More sharing options...
Uwe Posted December 6, 2013 Report Share Posted December 6, 2013 Hello, my question is: Why do you need this area? When I have "Groups" (maybe defined like a tag) and I can assign items to this "Group" then I would like to define in the User Administration e.g. user01:Administrator - that means no limitations user02:editor - that means all authorizations of the Editor and no limitations user03:editor:group01 - that means all authorizations of the Editor but only for the Group01. He can't neither see nor edit any other item in the catalog user04:reader - that means all authorizations of the Reader and no limitations user05:reader:group02 - that means all authorizations of the Reader but only for the Group02. He can't see any other item in the catalog ERP systems have a high sofisticated Authorization Management but that seems to be "overloaded" for the moment. Regards, Uwe Quote Link to comment Share on other sites More sharing options...
deanable Posted December 6, 2013 Report Share Posted December 6, 2013 I am looking forward to the implementation of this!!!! 'Access Restriction' and 'Access Control' for my vote. Quote Link to comment Share on other sites More sharing options...
Murat Posted December 6, 2013 Author Report Share Posted December 6, 2013 my question is: Why do you need this area? Restricted Areas (or whatever name we'll choose for this) allows you restict an access to different group of items. From one side feature will simulate "multiple catalogs" feature, and allows to hide a certain group of items from certain group of users. Of if you'll 10 designers or architects - each of them can work with his own set of items and don't see each others documents (but the Tag Vocabulary will be the same and visible for all users). 'Access Restriction' and 'Access Control' for my vote. Dean, thanks for the suggestion. But don't users think that this option is the only Restriction method in Daminion. Because we can also restrict an access via Roles. Quote Link to comment Share on other sites More sharing options...
Uwe Posted December 6, 2013 Report Share Posted December 6, 2013 Restricted Areas (or whatever name we'll choose for this) allows you restict an access to different group of items. From one side feature will simulate "multiple catalogs" feature, and allows to hide a certain group of items from certain group of users. Of if you'll 10 designers or architects - each of them can work with his own set of items and don't see each others documents (but the Tag Vocabulary will be the same and visible for all users). Hi Murat, I understood what you mean. My question was wrong. My question is: why does Daminion need a "restriction area" and the "group" when you have to define "groups" and then one has to assign these groups to the "restricted area". Is it not enough to link the "groups" directly to the user rights? What about: authorization control? Regards, Uwe Quote Link to comment Share on other sites More sharing options...
Murat Posted December 6, 2013 Author Report Share Posted December 6, 2013 I understood what you mean. My question was wrong. My question is: why does Daminion need a "restriction area" and the "group" when you have to define "groups" and then one has to assign these groups to the "restricted area". Is it not enough to link the "groups" directly to the user rights? What about: authorization control? The "Groups" term doesn't disclose what is behind this feature. Users might think that this is just a list of users "grouped by Groups". Quote Link to comment Share on other sites More sharing options...
exterminador Posted December 14, 2013 Report Share Posted December 14, 2013 My vote for "Access Control" , that way users can say for instance "Grant access" "Revoke access" which (imo) sounds familiar to Windows users. Regards 1 Quote Link to comment Share on other sites More sharing options...
rene Posted December 15, 2013 Report Share Posted December 15, 2013 I vote for "Access Control" as well looking Forward to this! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.