folder permissions and visibility problem

[Former Member]

Hello,

My problem is nearly identical to that listed here:https://scn.sap.com/thread/2137591

I made a folder named "FloorReports" and added a crystal report to it (2016 version).

I made a group named "Workers" and added a user named "worker_Joe" to it.

Back in Properties for the FloorReports folder, I added the Workers group to have "Schedule" level access.

From what I've read the "Schedule" level includes the access rights of "View" and "View On Demand". (reference: http://well-managed-business-intelligence.blogspot.com/2014/04/sap-businessobjects-security-access.h...

In my mind, when Joe logs into the BI Launch Pad, he should see the "FloorReports" folder and its contents. But alas - poor Joe cannot.

Note the properties of FloorReports initially had the "Everyone" group listed. And I attempted to do what was suggested in the first link at top - which resulted in Joe seeing *all* the folders! So I used the "Reset Security Settings" which removed the Everyone group. Instead of just resetting the permissions of the Everyone group, and leaving it in the list. (sigh)

So what step did I miss to allow Joe (and that group) access to that one folder and only that folder?

Thanks,

Aaron

[amitrathi239 · Accepted solution]

Check if everyone group has at least view access on the "All Folders".remove the inheritance from root folder for everyone group.

after that if you assign the group access on particular folder then user can see the folder

[Former Member · Accepted solution]

@Dell, yes the best practice model you described was my end goal.

@Amit, removing the inheritance check marks ultimately was the key to success.

I wanted a group I could add users to. And that group would only see one folder.

Side note: I kept getting errors from the Launch pad client on the networked vm saying "you do not have refresh rights" or something to that effect. Even though I had 'View on Demand' enabled.

Finally, in frustration and not knowing what else to try, I rebooted the client vm and server vm and that error went away!

That is definitely a bug but it would be hard to reproduce. But this info may help someone.

Thanks to you both for your help!

Aaron