1. Basic setup with Functional user categorization
This is the basic setup without any application/Department wise user categorization. Users will be categorized only based on their functionality (Viewer/Analyst/Author). This means users can view data across different applications and there is virtually no restriction on viewing the BI content. Functionalities enabled for each user category is described here in my previous blog BusinessObjects Administration - Setting up security model – An easy way to configure and manage
2. Hybrid setup with inherited user category
In this model, Users are segregated by each Application/department first. The subsequent user categorization would be additive in nature and the hierarchy will fall from least privileged group to most privileged group by making use of Group level inheritance capability. Similar to type 1 model, users of Application/department can view all the reports but only within their department.
Graphical representation of the model
3. Hybrid setup with cross Application/departmental & user category
This is the most effective and commonly used security model across various BusinessObjects deployments. Compared to previous two models this model ensures the BI content is accessed in a highly secured way i.e. reports are viewed by only group of users who are intended to do so. Here user groups within the department will be having distinct functional access rather than additive functional access as compared to that of type 2 model.
Graphical representation of the model
Let us see about each model in detail in upcoming blogs. Keep reading.
Related blogs
BusinessObjects Administration - Setting up security model – An easy way to configure and manage
BusinessObjects Administration - Setting up security model – Part III
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
6 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 |