An administrator can control the scope of filter constraints available to authors by defining them globally, or at the cabinet or folder level, and defining whether documents can inherit constraints defined at higher levels of the repository hierarchy or globally.
Organizations that maintain very large lists of filtering attributes may need to limit the availability of filtering attributes, based on the repository location of the document being edited.
Filtering attributes can be defined globally, in the 
Filtering folder in the Administration cabinet, in a single FilterConfig.cfg file. Additionally, filtering attributes can be defined at the cabinet level, or at a lower folder level within a cabinet by creating or importing FilterConfig.cfg files at these lower levels.
When configuring the system for filtering, if the administrator selects the Cumulative Filtering check box in the application document, specifications from any FilterConfig.cfg files in the ancestry of a folder (including the
Filtering folder in the Administration cabinet) are concatenated. This allows users who are authoring in the oXygen editor or the Workbench Map Editor to select any attribute and value inherited by the document.
If the Cumulative Filtering check box is cleared, users who are authoring in the oXygen editor or the Workbench Map Editor are limited to the attributes and values defined in the FilterConfig.cfg file located in the nearest parent folder or cabinet of the document or in the FilterConfig.cfg file in the Administration cabinet if constraints are defined globally.