When trying Content Access with Rules, I found that the "reset content permissions" action didn't go all the way to reset the permissions.
The permissions are reset to the configuration at the access tab for the content type, but I had to *resave* the node's acccess tab for the changes to take effect.
The "grant content permissions by role" (and also revoke) works just as expected.
Steps to reproduce:
* Enable per-node access settings for a selected content type.
* Add a reaction rule that changes the node access *on node view* (not node save), resetting them to default.
* Manually revoke the view access for anonymous users.
* View the node (as administrator).
* Inspect the access settings on the node's access page -> the anonymous checkbox is checked
* In another browser, visit the node -> you get access denied
* As admininstrator, again, save the tab with the access settings -> the anonymous user is allowed to view
I found these two issues relating to resetting permissions (though with different problems):