Permissions Reporter

Permissions Reporter provides advanced report filtering capabilities that can be applied either during or after the file system analysis.

 

Filters are useful for constraining the output of Permissions Reporter. For example, filtering can be used to report upon the file system permissions of a specific user or group.

 

Filters are comprised of conditions that must be met in order for permissions entries to be included in a report. Conditions are contained within groups, which can be arbitrarily nested to produce complex rule sets.

 

Project Scan Filtering

 

When you modify the filter for the current Permissions Reporter project and then run the project, your filter rules will be applied during the file system scanning process.

 

Scan-time filtering affects the amount of actual data stored in memory. Folder and permission entries that don't match the current project filter will not be stored, thereby reducing the program's overall memory footprint. The larger the file system analysis workload, the more these memory savings tend to show themselves.

 

To apply scan-time filtering, click the Filter button in the main window toolbar and select Edit Project Scan Filter.

 

Post-Scan Filtering

 

You can also filter the results of a permissions report after the scan completes. You do this by clicking the Filter button in the main window toolbar, and selecting the appropriate option.

 

To apply post-scan filtering, click the Filter button in the main window toolbar and select the Edit Post-Scan Filter option.

 

Filter Groups

 

Filter groups are used to determine whether report permissions match ANY or ALL conditions specified within the filter. They control the match scope of both child conditions and child groups.

 

Filter groups can be nested to create arbitrarily complex rule trees, each with their own match scope and conditions.

 

Filter Conditions

 

Filter conditions allow you to specify the criteria against which filters are tested - they must match in order for permissions to be included in a report.

 

Each condition has a type (e.g. "Account name", "Account enabled", etc.), an operator (e.g. "Is equal to", "Is not equal to", etc.) and a value. When the condition type if selected, the operator and value inputs will change accordingly.

 

Filter conditions are defined by clicking the Add button next to a filter group.