Sorry, still confused about "Keep"

Would unchecking the "keep" box and hitting save simply flush all (3?) possible flags? Seems like a shortcut for no reason at that point.

I must say I agree. I know there must be good reasons for the way it is, but I am coming at this from having to hand this over to a client, and having to explain what this checkbox is.

I have read some of the explanations for it, but explaining this to a client is troublesome. Seems to me "Keep" should be assumed, and if we wanted to "remove" or "delete" then that should be a separate, discrete action. That would be clearer and easier to explain.

agreed: "Keep?" is strange. Module needs some UI/UX work. If you uncheck it then click "save grants", it removes the user from grants.

I need to chime in here and say that Keep? is totally ambiguous and having read the posts from others asking what is Keep? I am still none the wiser.

Apart from the maintainers, does anybody actually know the answer?

I ended up here, trying to see why nodeAccess doesn't work in my case. I want to provide edit access for nodes to specific users.

The problem I have is that this 'Keep?' checkbox is nowhere to be found for me. Although I do see the message, and I googled that message cause I want to see whether this is why nodeAccess doesn't work as intended (whatever I try, selected users put in the autocomplete and given grants, do NOT have edit access).

Any help?

I use D8, and 8.x-1.0-beta2 version of module.

---

EDIT - I did find it, I never pressed 'search' before, because I always typed in my test-user and clicked on the auto-completed name. It is not straight-forward that you *should* click search before all checkboxes appear. I leave my comment here in order someone else has the same problem in the future and ends up here. However, I would suggest that for user experience, it shouldn't be this way, check boxes should be there already, and if it's not possible, at least inform the user that he should click search, even if searching for the username is not necessary.

I initially made the same mistake myself. Perhaps the search button would make more sense if labelled 'Confirm Selection' or something similar.

As far as Keep? is concerned, and given that it is enabled by default, I have chosen to hide it with css. Not ideal by any means, but it seems to be working for my use case.

The css was not straight-forward as the module has not been written with theming in mind, so I had to use nth-child selectors to target the second cell of the table header and each row.

The problem I have with Keep is that the UI makes it look like "Keep" is a permission, like "view", "edit", or "delete". As far as I know it isn't. But I don't really know what it even means or does. All I know is to always leave it checked except when you need to delete a grant. It's even more confusing given that there is a checkbox called "Delete", so it is possible to check both "Keep" and "Delete". That's just confusing.

On Drupal 7 I also see that if I un-check the keep checkbox and click on save grants, nothing happens. On page refresh the checkbox reverts to checked state. Weird behavior. I prefer to hide the checkboxs using CSS as it is of no use.

#nodeaccess-grants-form table:nth-child(6) tr th:nth-child(2), #nodeaccess-grants-form table:nth-child(7) tr th:nth-child(2), #nodeaccess-grants-form table:nth-child(7) tr td:nth-child(2) {
	display: none;
}

• Checked `keep` means keeping the custom grant settings to the target user per node AFTER saving -- keep this row / keep this grants.
• Unchecked `keep` means deleting/removing the custom grant settings to the target user per node AFTER saving -- delete this row / delete this grants.

2.0.x is the latest dev branch.

So let's end up here after 4 years without a new comment. Agree to improve the UI, but not in this issue.