Several factors should be considered when you are setting up the cabinet structure in the repository.
Administrators can create cabinets within the repository. All cabinets in the repository are siblings in the repository hierarchy; that is, a cabinet cannot contain another cabinet. Each cabinet can contain a hierarchy of folders and other repository objects.
Each user can control which cabinets are shown or hidden in the Navigation view.
You may create separate cabinets in the repository to contain all of the objects related to a particular project.
An administrator can apply access controls to a cabinet so that only authorized users or groups can alter the cabinet properties, contents, or other characteristics. Objects within the cabinet hierarchy inherit the access controls applied at the cabinet level unless explicitly overridden at a lower level of the hierarchy.
Objects within a cabinet can reference or be referenced by objects in another cabinet.
Task Sequence and Audience Parameters documents located at the top level of a cabinet can define workflow and audience details for a project.
If the repository is configured to use the wastebasket feature, each cabinet can specify a retention period for deleted items before they are permanently destroyed.
You can limit the scope of a Saved Search or a Basic Search to the contents of a cabinet.
You can control the scope of filtering constraints that are available to documents residing in a cabinet.