This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Comprehensive report to expose all subordinate users of an AD user

I am looking into a customer request (Iron Mountain) for a report which would enumerate all direct and indirect subordinates to an AD user to the bottom most level. Their use case is primarily centered around constructing and altering distribution lists for disseminating communications from upper management and department heads down to all relevant employees. Any help in constructing something would be greatly appreciated. Thanks in advance! 

Parents
  • Hello Peter, 

    Thank you for your request.  This one is interesting.  As you know we do collect the managed by attribute for each AD user and could build a report based on this.   

    The issue will be with the layout of this report.  Since there could be a large number of management levels, how do you see the layout looking?   If the main purpose is to show a distribution list based on a root manager, I would highly suggest a flat list of all direct and indirect subordinates.   E.g.   Run the report for the manager "Angela Freeman" and get a flat list of all direct and indirect reports.   Similar to a recursive membership report, we need to understand if you need the report layout has to display how the indirect report was found (membership path). 

    Manager: Angela Freeman

            Direct Report1

            Direct Report2

            Indirect ReportA

            Indirect ReportB

    Also note that depending on the number of AD users and the number of management levels we will optimize the query for the best performance. 

    Let me know your thoughts on layout and we can then look further. 

    Thanks,

    -Angela

  • I thought it was an interesting one as well. For the use case at hand, I can verify that a flat list would absolutely suffice and having a report showing the membership path would be icing on the cake. I imagine there are used cases that would necessitate the more in-depth report as you've described, however I cannot remember one from any discussions lately. Thank you!

Reply
  • I thought it was an interesting one as well. For the use case at hand, I can verify that a flat list would absolutely suffice and having a report showing the membership path would be icing on the cake. I imagine there are used cases that would necessitate the more in-depth report as you've described, however I cannot remember one from any discussions lately. Thank you!

Children
No Data