Beruflich Dokumente
Kultur Dokumente
Background
1. Contact
2. Personal
3. Sales Rep
4. Manager
5. Organization
6. All
7. Admin
Summary
1. Personal Visibility:
This implies that the users can see only the records they own. This is used when the ownership is
based on employee or position ownership. Example: standard My Activities view.
2. Contact Visibility:
This type of visibility is used for eService users or eApplication users to see the records based on
their contact ID. Example is "My Service Request" view in eService application.
Configuration required:
At view level:
This is also known as team based visibility. The user can see all the records where he or she is on
the team. This does not look for the primary position on the team. The team is defined a multi-
value field based on position. Example is "My Contacts" View in Siebel Application.
Configuration required:
At view level:
Visibility Emp MVField: Name of the position multi-value field using the multi-value link
position.
Visibility MVLink: Specifies the position multi-value link.
4. Manager Visibility:
This visibility allows manager to see their own records and the records of their subordinates. If
this visibility is based on team ownership, managers can see the records where subordinates
reporting directly or indirectly to them are the primary members of the team.
For Example: "My Team's Accounts". For views where visibility is based upon employee or
position ownership, all records owned by the manager and the subordinates are displayed. The
Example is: "My Team's Activities view".
Configuration required:
The configuration remains same as above except that the Visibility Applet Type needs to be set
up to Manager.
5. Organization Visibility:
This is a new type of visibility introduced in Siebel 2000. This allows users to see any records
that are associated to the same organization as their current position. Example is "All Accounts
view" or "All Contacts view". The business component might be related to one organization or
many organizations. So the link could be many-to-one or many-to-many between the business
component and organization.
Configuration required:
At view level:
6. All Visibility:
This shows all the rows in the database for employee or position ownership views. For position
team views, only the records, which have primary team member on the team, would be shown.
Example is "All Accounts Across Organizations"
Configuration required:
The configuration is same as SalesRep or Manager except that Visibility Applet Type is set to
"All".
7. Admin:
Show all the records existing in the database. All the visibility settings are ignored. The only
configuration required is to set the "Admin Mode Flag" property to “True” at the view level. This
view is used to find and maintain records. These views are generally placed on admin Screen.
Example would be: "Account Administration view".
Please note that these visibility settings might not work for the specialized business components
as the visibility is sometimes driven by the hard coded C++ code behind these specialized classes.
Please refer to Siebel Tools Guide version 6, chapter “Controlling Access to Information” for
more information regarding visibility types and configuration properties related to visibility.
Siebel 7 (Enterprise)
In Siebel 7, the configuration properties for the visibility property settings have slightly changed.
Also, some new types of visibility have been introduced. For more information about the new
types of visibility and the visibility configuration properties for Siebel 7, refer to “Authentication
and Access Control Administration Guide” Version 7.0, chapter “Basic Access Control”.