When attempting to set Object Authorizations on an object at object level, the object can't be saved a red exclamation triangle shows up on the Object Authorizations panel of the object. Hovering over this exclamation show a message: Write permission (W) must be given to you or to a UserGroup you are a member of.
Version: All
The user who is putting Object Authorizations in place needs to have write access put in as well - Please see the warning below before putting this in place
We would highly recommend against using Object Authorizations on an object level. This is because setting authorizations on an object level will implicitly deny authorizations for all other users or usergroups. This also means if that user is decommissioned, no one will be able to use that object. It will always be a better option to add the object at the user level if it's an exception for just that user or set it a the usergroup level if applicable as well.
The documentation notes this as well: Note: Defining authorizations at an individual level is not the recommended method to design a solid and easy-to-maintain user management policy in your company. The recommended method is to define User Groups, assign them Users and grant authorizations and privileges to the User Groups. Take into account that combining User and User Group rights with additional object authorizations can lead to contradictory definitions. Use object authorizations sparingly..
If authorizations absolutely must be put on an object in the Object Authorizations panel of an object, then the user putting those Authorizations on needs to have their own user or usergroup be put on with Write (W) authorization