Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Siebel Analytics Installation and Configuration Guide > Applications User Authentication and Security Setup > Integrated Security for Responsibilities and Groups >
Data-Level Security
Data-level security defines what the application user sees inside a report. The same report, when run by two different users, can bring up different data. This is similar to how the My Opportunities view in a Siebel operational application displays different data for different users. However, the structure of the report is the same for all users, with one exception. The exception is when a user does not have access to a column within a report. This is a rare case; Siebel Analytics handles this situation by returning the report without the column in question.
Data-level security is configured exclusively through the Analytics repository using Repository groups (the equivalent of Siebel responsibilities). It is configured at the logical layer, mostly on dimensions. The Fact tables, other than the most sensitive Revenue facts (Closed Revenue, Opty Revenue and Expected Revenue), are not secured directly. However, dimensions are secured, as shown in Table 13.
The security definition for the dimension decides the general area within which the user operates. The reports can further restrict access to the data within the report. For example, if a report contains a filter such as Employee.Login = valueof (USER), then this restricts the rows returned in the report to those where the user is the owner of the record.
Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Siebel Analytics Installation and Configuration Guide, Version 7.5, Rev. C Published: 18 April 2003 |