Hello @jonatan.bergstrom !
The permissions of the parent folder are inherited by default in case permissions for paths inside the folder don’t explicitly mention a principal, e.g.:
/some/folder ACLs are “group1”: “rw”, “user1”: “rw”
/some/folder/file ACLs are empty
^ in this case /some/folder/file ACLs are effectively the same as for /some/folder. When the ACL check is being done for each operation (read or write), a principal is selected - it’s either a username or any of the groups this user belongs to. In case the principal is not explicitly mentioned in the ACLs for a given path, the parent path is checked recursively until the root is reached (in which case the default behavior is “denied”).
WRT the ability to change ACLs for multiple files: do you mean an ability to recursively change ACLs for a given folder or do you mean shift-selecting multiple files/folders within a folder and changing ACLs just for the selected paths?