Professional Documents
Culture Documents
Module 6 Controlling Access To Customer Data
Module 6 Controlling Access To Customer Data
0 Essentials
1 of 23
Module Objectives
To understand the difference between Customer data and Master data
in Siebel applications
To learn the different Access Control mechanisms used to restrict
access to data in Siebel applications
To identify the different view types for different types of users
3 of 23
Business Requirement
Users should be able to perform the same job function but on different
sets of data
For example, sales representatives need access to records of their own
accounts, but not to others
There should be restricted access to data
Users should be able to easily locate required records
Users should be able to see only those records required for their job
4 of 23
User productivity
5 of 23
responsibilities, but may see different sets of data in the view, defined
by the access control mechanism
6 of 23
Data Classification
Data in a Siebel Enterprise is classified as either customer data or
master data
Customer Data:
consists of dynamic data, such as service requests and opportunities
7 of 23
a combination of these
Data visibility is determined by the properties set at the underlying business
component (BC) level
Visibility is restricted to one or more employee, position or organization
8 of 23
9 of 23
My Views
My Views show records where the user or his position is directly
10 of 23
My Teams Views
My Teams Views is an additional view for managers that allows them
In My Teams Contacts,
the manager sees
records assigned to
direct or indirect reports
11 of 23
All Views
All Views is used to display all records belonging to the current
12 of 23
13 of 23
14 of 23
an organization
It is restricted only to those users who need to access records across
the whole company
15 of 23
Administration Views
Administration views display all database records; even those
16 of 23
17 of 23
18 of 23
mechanism
Each view is preconfigured to use only one mechanism at a time.
If another mechanism needs to be used, one has to create and configure
another view
19 of 23
Examples
1. An employees position may be assigned to an account that is not
20 of 23
Single-Valued
Access
Multi-Valued
Access
Employees
Service Requests
Expense Reports
Contacts
Assets
Activities
Positions
Forecasts
Accounts
Contacts
Opportunities
Quotes
Organizations
Assets
Consumers
Forecasts
Accounts
Opportunities
Quotes
21 of 23
Module Highlights
Access to records may be restricted by employees, positions,
22 of 23
Lab
In the lab, you will:
Explore record visibility in the application
Examine how adding a position to a user affects the various visibility filters
23 of 23