Separate documents and records with different level of privacy.
Teams need to deal with information on different levels of privacy.
Adding new pages to a space that is publicly accessible, but the information on the page is confidential may someday reveal information unintentionally. While this is less a problem on official pages where access privileges are of major concern, spaces dedicated to team communication typically do not have the time to rate the privacy status for each piece of information.
Therefore the level of privacy should be defined for each space. The number of spaces is much smaller than the number of pages. Teams typically handle a small number of categories of spaces. So it is much easier to remember the privacy level and add the information to the right spaces.
Makes it easier - especially for team communication - to handle the level of privacy appropriately.
The simplification is not applicable for every use case. Especially where the number of spaces is limited, users need to handle access restrictions based on page trees.
The following practices are related to this practice.
- Frequency of Change
- Consider content by the frequency of change. Group content in information sets that change in the same frequency. The most important category for changes is the record, which implies no change.
- Make Reader feel Home
- Communicate in a way expected by the reader.
- Physical Location
- Store information physically only by properties that are invariant.