My original need for the separation was similar to that in the User-specific filters:
- A person creates a row for themselves (usually through a button, so they’re not really aware they added a row — it was a part of their “login flow”, so to say)
- They see that row throughout the doc as the one hosting their user-specific controls.
- They accidentally delete it by misclicking, selecting the whole row instead of one cell, and pressing Del.
Some of the pages that will have that user-specific view will be the pages with Add Rows permission turned on. Unfortunately we can’t apply locking to individual objects but to the whole page. So technically that permission will allow the user to accidentally do the above.
Ideally there’s a per-view locking.
But with the model we have right now, I’d say Add Rows should not include the Delete Rows feature. That said, Undo should work for those accidental row adds. Otherwise doc makers should expose a per-row button to Delete Row that they can set up with whatever conditions that make sense for them (e.g. disable the button on rows created by someone else etc.)