No indication to save or "Commit changes"

My use case: Adding users to the ACL for a specific node for "View" only permissions.

I know it says it in the fieldset description, but i was still caught not doing it right. I added a user and spent a few minutes trying to figure out why access wasn't being granted to the user. Then I remembered to click "Commit updates." This is a little confusing because when I click "Add user" it adds the user immediately making it appear as though that's all I had to do. Additionally I can leave the page, NOT committing update, and not be aware that my users that I just added are lost.

Possible solution: I notice, at least in my environment, that when I click on "Commit updates" it leaves me on the same page. I wonder then if the "Add user" function could be considered redundant? Perhaps change "Commit updates" label to "Add user." That is...commit as I go (add). Or make "Add user" commit at the same time. Although, I'm only looking at this from my use case. If other sites want to include view, update, delete for their node authors then "Commit updates" for all three at once makes sense. But, even then there's nothing telling the author that he/she has not committed the updates.

A thought as I continue playing with this. How about a message next to every new user added that reads: (not saved).

Bill
Jane
Cory (not saved)
Stacey (not saved)

Or a general message "You have unsaved changes" that triggers when one new user is added and remains until the user commits changes. Somewhere in the ACL fieldset. That would be for my use case. For any use case upon any changes should cause this trigger.

Of course the bigger concern is when node authors "Remove" a user. They are going to be pretty upset if a week or so later they discover that the user they thought they removed still has access to the node.