Support Custom Attributes and Dataset Extension in Reports

Products Auditor Ideas
,
1

What is a one sentence summary of your feature request?

Allow administrators to add custom attributes and create additional datasets for Risk Assessment reports, enabling inclusion of fields such as account creation date (whenCreated).

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

Currently, report customization is limited to the attributes already included in the predefined datasets. While report templates can be modified, it is not possible to add new columns based on attributes that are not exposed through the existing dataset structure.

For example, in the Inactive Users report, it would be useful to include the Active Directory whenCreated attribute to identify accounts that have never signed in and determine how long they have existed. This would allow organizations to create more meaningful reporting logic, such as highlighting accounts that were created more than 90 days ago and have never been used.

A valuable enhancement would be the ability to extend existing datasets, create custom datasets, or map additional directory attributes to reports without requiring changes from the product vendor. This would provide greater flexibility and allow organizations to adapt reports to their own security and compliance requirements.

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

Currently, there is no supported way to add attributes that are not already present in the report dataset. As a result, we are unable to include important fields such as whenCreated in the report and cannot implement the desired reporting logic without product-level changes.

2

Thank you for this request, Ali!
This highlights a well-known limitation in our reporting engine: the dataset boundary that prevents adding attributes not already mapped. The ability to extend datasets or define custom data mappings is something we have heard from multiple customers and is on our long-term roadmap for the reporting and Risk Assessment modules. We understand that created example is a common use-case organizations often need to distinguish between newly provisioned accounts and genuinely abandoned ones. As an interim option, you may be able to supplement Auditor data by exporting report results and joining them with AD data (e.g., via PowerShell + CSV or by querying the Netwrix Auditor database directly) to add the missing attribute. This is not ideal but can fill the gap while we evaluate native dataset extensibility.
We are logging this request and will factor it into our reporting roadmap discussions.