Hi bud.
For sure this is a question of what is really important to the customer, not really how deep is the documentation you deliver at the end of the project.
In my opinion, we need to understand that most of people at the customer that will read the documentation are not tech people, so we need to focus on the clarification of how the CPPM treats the access and how the endpoints are categorized, despite the technical way this has been done. In order to achieve this balance, usually I make two documentation packs: one strictly technical (with the backup info, service profile and role associations, etc) and one showing the global view of the environment.
This way we can provide technical informations and valuable resources to technical support and the same way to the C-Level reading.