Ability to share Personal Folder content in OBIEE to a broader group of folks (but still contained)

3371002

Initially, I had decided to create a Distributed Development Folder and give access as needed to the content. Following though are a couple of simple use cases I can see where, what if they want to share it with a set list of people and don't want to just put it into a fishbowl for everyone to see?

• As an author in a distributed unit, I want to create a dashboard or analysis that I can share with a colleague for feedback
• As an author in a distributed unit, I want to publish a dashboard or analysis for my peers to use for daily operational tasks
• As an author in a distributed unit, I need to create a dashboard/analysis for my CEO that she needs by EOD

Is there a way for users to share content they develop on a more ad hoc basis and control who can see it?

Chris Arnold

Could you give each user their own folder in the Distributed Development Folder, and then let each user give permissions to any analyses or subfolders they have in their own folders?

Maybe I am over simplifying and not totally understanding the issue.

Joel

Personal Folders are just that - they are only accessible to the owner. If you want to share content, then the Shared Folder structure should be utilized. You can set the permissions on the Shared Folder to ensure that it is only accessible to the correct audience.

Thomas Dodds

set up your web catalog something like

/Shared Folders/Sandbox/Department  <-- for department level access to stuff that group wants to share among themselves; use BI roles membred by AD groups to control visibility and content contribution permissions

example:

/Shared Folders/Sandbox/Finance

Roles:

BIConsumer

BIAuthor

Finance <- granted access to folder

content contributor is in roles:  BIAuthor & Finance

content consumer is in roles: BIConsumer & Finance

content consumer that can see finance and hr is in roles:  BIConsumer, Finance & HR

Gianni Ceresa

Thomas gaves you a good example.

Just a note (as you can see in the example): you set permissions to the required application roles but you don't add a permission as "no access" to all the other as you have too many side effects. So really better if you don't set any "no access" and just add the minimum required app roles with their permission (all the missing app roles will not have access, except for users in multiple app roles etc.).

3371002

use BI roles "membred" by AD groups - what is the word you intended to use here?

Thomas Dodds

"membered" ... put user ids into groups and member your EM BI Roles with groups - not individual user IDs ...