About Single-Organization and Multiple-Organization Access Control
Depending on the type of data, you can associate one or more organizations to individual data. The user can see data that is associated with the user’s active organization. For example, in the All Service Requests view, a user can see all the service requests associated with the user’s active organization.
For data that can be associated with multiple organizations, one of the organizations is designated as the primary organization. The primary organization is a factor in suborganization access control, but not in multiple-organization access control.
The information in the following table lists data on which you can apply organization access control and indicates, for some of the most commonly used Siebel objects, whether a single organization, or multiple organizations, can be associated with the data.
Object Type |
Object |
Relationship |
---|---|---|
Customer data |
Account |
Multiple |
Customer data |
Competitor |
Multiple |
Customer data |
Contact |
Multiple |
Customer data |
Forecast Series |
Multiple |
Customer data |
Household |
Multiple |
Customer data |
Marketing Event/Activity |
Multiple |
Customer data |
Opportunity |
Multiple |
Customer data |
Order |
Multiple |
Customer data |
Partner |
Multiple |
Customer data |
Product Defect |
Multiple |
Customer data |
Project |
Multiple |
Customer data |
Quote |
Multiple |
Customer data |
Service Request |
Multiple |
Customer data |
User List |
Multiple |
Referential data (includes master data) |
SmartScript |
Multiple |
Referential data (includes master data) |
Literature |
Multiple |
Referential data (includes master data) |
Price List |
Multiple |
Referential data (includes master data) |
Cost List/Rate List |
Multiple |
Referential data (includes master data) |
Period |
Single |
Referential data (includes master data) |
Product |
Multiple |
Referential data (includes master data) |
Catalog |
Not Applicable (catalogs use access-group access control) |
Administrative data |
Employee |
Multiple |
Administrative data |
Division |
Single |
Administrative data |
List of Values Type |
Multiple |
Administrative data |
List of Values |
Single |
Administrative data |
Position |
Single |
Administrative data |
Responsibility |
Multiple |
All (but not All across) is frequently in the title of views applying single- or multiple-organization access control. For example, the All Contacts view applies single-organization access control, and the All Product Defects view applies multiple-organization access control. However, All does not always imply single- or multiple-organization access control. Some All views apply All access control. For example, the All Service Requests view applies All access control.
A business component’s view modes determine whether single-organization or multiple-organization access control can be applied in a view that is based on the business component.
To have single-organization access control available, a business component must have a view mode (typically Organization) of owner type Organization with an entry in the Visibility Field column (instead of the Visibility MVField column).
To have multiple-organization access control available, a business component must have a view mode (typically Organization) of owner type Organization with entries in the Visibility MVField and Visibility MVLink columns (instead of the Visibility Field column).
For information about All access control, see About All Access Control. For information about business component view modes, see Viewing Business Component View Modes.