I am implementing a new customer and the topic was brought up permission set vs profile administration.



Obvious reason permission sets is the route to go. And, this is what we ultimately decided on as you do not have to go in and make edits monthly.



However, their use case was that they try not to utilize permission sets in the SFDC org. While it is entirely possible to utilize profiles for everything that the permission sets do it is difficult to maintain. They were ok with this but, they were mostly ok with this if the release notes had the updates of what is being added/edited.



I verified with product that we currently only update the master sheet on support docs. Not stating that this was effected this release vs another release.



A simple line on the bottom of the release saying, "Permission to this field on this object added to this permission set" is all it would require.