-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
compliance team-report
empty columns: number of records & shared folder names
#1054
Comments
Thank you for reporting issues with the compliance report.
It is a known issue if your shared folder has only teams. Adding any user to the shared folder fixes compliance report output.
Shared folder names come from the vault of the currently logged in user. This information is not stored at the enterprise level. |
Good to know! I'll add a user that's already added via a team to the shared folders, cheers. :)
Makes sense when thinking of least-privileged, but it's unfortunate that we can't create reports that show which shared folders are being created by the end-users. I'm looking for a way to monitor/manage all shared folders within an MC (including the ones shared directly with individuals, rather than teams). |
Audit reports can be used for monitoring shared folder activity within an MC. The audit data available only for one MC at the time currently. It would not be hard to let MSP retrieve audit events for all MCs at the time. |
Thank you for your suggestion. :) If there would be a way to report shared folder activity on the MSP level over all MCs, that would save me some time. |
Hi there!
Using version 16.9.8, when I run the command:
compliance team-report -r -nc -tu
Both at the MSP level and the MC level the number of records column displays "0".
The shared folder names are missing only for the MC level.
I've tried this at several MCs, same result for when there's 1 team or many.
For readability, I've attached the debug logs in spoiler tags below:
MSP debug output
MC debug output
If there's anything else I can do to provide more info, please let me know. :)
The text was updated successfully, but these errors were encountered: