Forum Discussion
Nested Security Groups
Sorry to loop back to this but wondering if anyone else has come across it and found a fix? We seem to have hit the same issue again.
I did log a call with MS support but had to give up on it, they wanted me to collect fiddler traces for a user with issues that proved to be a real pain to manage (and I couldn't see how it would help as the issue must be server-side)
I have the same issue - a set of reports that I want to give different people different access to using security groups aligned to their roles and level of access.
People in the main security group can access reports but people in another security group which is a member of the main group (nested) cannot access.
I really don't want to have to expand out all the reports access - is there any update on this bug fix
There doesn't seem to be an ideal solution.
If you have your dataset and reports in separate workspaces you have to make sure there are matching security groups applied to each. You can't use the parent group on one and the subgroup on the other.
