What is a one sentence summary of your feature request?
Allow multiple exclusion of Group, User, OU, UNC Path, etc from Reports.
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
Certain fields can already filter out user, group, or computer objects with “%[]” like %[Domain Admins] or %[^$]. Adding a comma[,], semi-colon [;], pipe[|] character inside or out of the %[] like “%[Domain Admins]|%[Domain\UserAccount]” where the pipe can be replaced for whichever character you choose or “%[Domain Admins, Domain\UserAccount, ^$, Administrators]”
How do you currently solve the challenges you have by not having this feature?
I use a series of powershell scripts to obtain the groups and users and their permissions on my DFS shares, then I export the data into a format I prefer using Export-HTML, then I use another powershell script to convert the .html files to .pdfs.
Upload any supporting images that you think should be considered in this idea.
1 Like
Thanks for laying this out and for including the exact format you’d want to type it in, that’s genuinely helpful. Makes it a lot easier to picture what you mean instead of guessing.
Sounds like excluding one group or user at a time works fine today, but once you need to leave out several at once, there’s no way to do that in a single filter so you end up building the whole permissions report yourself with scripts just to strip out the accounts you don’t want to see.
Letting people list several exclusions at once, separated by a comma or similar, seems like a reasonable improvement and it’d probably be useful well beyond DFS shares, anywhere you can filter results today.
I’ve logged this for the team to look into. Can’t say yet exactly how it’ll work under the hood, but the way you described it and what you’re stuck doing manually right now gives us exactly what we need to scope it properly.
1 Like