Add the ability to export reports grouped by a selected field based on available data in report

Auditor Auditor Ideas
, ,
1

What is a one sentence summary of your feature request?

Add the ability to export reports grouped by a selected field.

Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.

I am performing a SOC 2 Type 2 audit and must perform monthly access reviews for users who have access to DFS-hosted file shares. Each month, I generate permission reports and distribute them to department managers so they can review and certify access for the users they manage.

Currently, the Folder Permissions with Account Details report includes the Manager attribute from Active Directory, which is exactly the information needed to route reviews to the appropriate approver. However, there is no way to automatically export the report into separate files based on the Manager field.

Because of this limitation, significant manual effort is required to filter, separate, and distribute review data to individual managers each month.

Example Workflow

  1. Auditor generates a Folder Permissions with Account Details report.
  2. Auditor selects Save/Export.
  3. Auditor chooses an export format (PDF, Excel, etc.).
  4. A secondary option appears: Export by Field.
  5. Available fields could include:
    • Manager
    • Department
    • Permission Type
    • Group Membership
    • Direct Access
    • Other report fields

Manager Example

When Manager is selected:

  • Netwrix automatically generates a separate PDF for each unique Manager value.
  • Each PDF contains only the users managed by that specific manager and the file share permissions those users possess through either:
    • Direct permissions
    • Group-based permissions
  • Accounts with a blank or null Manager field are grouped into a single PDF (for example, “Users Without Manager”).

Output

The generated PDFs are packaged into a ZIP file and made available for download.

Benefits

  • Significantly reduces manual effort required for access certifications.
  • Improves support for SOC 2, SOX, HIPAA, and other compliance-related access reviews.
  • Enables manager-based attestations directly from report output if signature, printed name, and date fields were added.
  • Provides a scalable solution for organizations with large numbers of DFS shares and managed users.
  • Leverages existing Active Directory attributes already present in the report.

Use Case

As an auditor, I want to generate permission reports and automatically split the output by Manager so that each manager receives only the access information relevant to the users they supervise, enabling efficient and auditable access review and certification processes. Adding a subscribe step, if requested feature was implemented, might automate this process further by emailing permission access by specified field directly to a recipient.

How do you currently solve the challenges you have by not having this feature?

I use a powershell script to pull the data and export to an html file, then use another powershell script to convert the 170+ html documents to PDFs. A final script generates Draft emails that contain the PDFs and the manager’s email address in the “to:” field along with instructions in the body, “CC:”, and “BCC:” fields.

1 Like
2

Hi!
Thank you for putting this together. This is one of the clearest feature write-ups I’ve seen come through here, and honestly the workflow you described (three separate scripts just to get PDFs into managers’ inboxes every month) is exactly the kind of manual grind we want to get rid of.

Splitting a report by a field like Manager, and having each manager only see the users they own, makes a lot of sense, especially since the report already pulls that Manager attribute from Active Directory, so we’re not asking for new data, just a smarter way to package what’s already there. The idea of a “no manager assigned” bucket is a nice touch too that’s the kind of edge case that usually gets missed until someone hits it in a real audit.

I’m going to log this as a feature request so it gets proper visibility with the team.

I can’t give you a timeline yet hat’ll depend on prioritization against everything else on the roadmap but your write-up gives us everything we need to scope it properly, so nothing here gets lost in translation. If other people run into the same monthly grind, encourage them to upvote or comment on this post hat visibility genuinely helps when we’re deciding what to build next.

Thanks again for the detail, especially the example workflow and the “how do you solve this today” part. That’s often the most useful for us.

3 Likes