{"id":325,"date":"2016-09-19T10:07:43","date_gmt":"2016-09-18T22:07:31","guid":{"rendered":"http:\/\/help.psoda.com\/?page_id=325"},"modified":"2023-08-16T02:28:29","modified_gmt":"2023-08-16T02:28:29","slug":"a170","status":"publish","type":"page","link":"https:\/\/www.psoda.com\/help\/a170\/","title":{"rendered":"Access Control Lists (ACLs)"},"content":{"rendered":"
Access rights are allocated to a security \"Group<\/a>group<\/a> by adding \"Key<\/a>Access Control Lists (or ACLs) to that group.\r\n\r\nAn ACL is a set of permissions that is attached to an asset<\/a> in the Psoda database, for example a particular \"Programme<\/a>programme<\/a> or \"Project<\/a>project<\/a>. The ACL defines what exactly the members of the parent group are allowed to do to the selected asset and all of its child assets.\r\n\r\nFor example an ACL related to Project A could limit the group members to only view comments on that project, but not to make any changes to those comments.\r\n\r\nA particular security group can have any number of ACLs, but it can only have one ACL for any particular asset in the database. I.e. you cannot have two ACLs in one group related to the same project.\r\n\r\nYou can however have an ACL in a sub-group for the same asset as an ACL in the parent group. In this case the sub-group’s ACL would take precedence for members of the sub-group but would not affect any members of the parent group.\r\n\r\nTo add a new ACL you first have to view the group that you want to add the ACL to and then use the “Add<\/strong>” menu button in the top header area for that group.<\/div>\r\n

Related topics<\/h4>\r\n