Forum Discussion
When should users break inherittance?
I've always advocated that SharePoint inherittance should be broken in the following order; site collection, site, library, document set, folder, document. In other words only break at document level...
Isn't the new answer is that users should break inheritance whenever they want? After all, there's a really easy mechanism provided for users to "share" a doc, and by default, sharing will break permissions as needed, as will several of the options in the dialog for getting a link to a doc. If you don't want users breaking inheritance, then what are you doing to keep them away from the sharing and "get a link" functionality?
If inherittance is broken at site collection or site level then all of the information below is invisible to everyone else, which may be required but if it is information that users should be able to see and permissions are being given on a document by document basis then collaboration and innovation becomes restricted hence my question asking if anyone has come across some decent training/education material to assist users in choosing the right option