To prevent users from changing the name of the planet, you can develop a Item Updating event receiver.
Martin's solution is very straightforward but you can also expand on this by using content types to allow for an approval process that performs another action.At your disposal on SPRemote Event Properties you have after Properties and before Properties, found by doing this: And those were the key to the problem: how to act on the firing only when the user changes something and not when it updates itself? You can also use event receivers to validate the data that the user wants to change. I want to trigger a workflow only when a value is updated in a list item, but not everytime the item is changed.For example I have a column for approve/not approve and I want that to be the trigger not the other values in the item.Item Updated I did an Update and making it trigger itself. If you’re dealing with a event receiver with access to server side code, this is not a problem.