If one uses with as a client module to restrict access to a specific node for a specific user. Since ACL only provides an API, and this feature request only concerns the user interface, I understand that it belongs in the Flexi Access issue queue.
The normal behaviour on my site is that authenticated users are granted view access. However, sometimes (this is rare) a specific user is disqualified from viewing a specific node, so I need to be able to remove view access for that node for that user.
I understand that the Drupal philosophy with respect to access control is cumulative. If "something" says that you should be granted access, you are. In order to exercise per-user access control, you need to first take it away, and then add it back for the specific user (e.g. by means of the functionality in the module).
+ has enough fine-grained control to let me exercise per-user access control. However, in order to do this, I must first turn off access for all roles the user belongs to (using role based access control settings), then enable per content node access control settings for the content type, and then visit each individual node, click on the access control tab, expand the user access control lists panel, and finally manually grant access to authenticated users on a one-by-one basis. This last operation is very time consuming.
What I am missing is a way to set up a default access control list for a content type. The module has a UI that allows me to establish default access permissions for each Role. But there seems to be no way default access permissions for each User.
I want to be able to define a default access list with users that has view access granted that is automatically applied whenever I create a new node that has per content node access control settings enabled. Then, only in the very rare cases where I want to depart from the default would I have to intervene to remove someone from the access control list.
(And if there is an alternative way to accomplish something similar, I am interested in hearing about it.)
Active
1.0
User interface