|Bookshelf Home | Contents | Index | PDF|
As part of implementing an access control strategy for your application, you must define your company's structure, outside partner relationships, and so on. You also define the types of data and objects that people will need to access and work with to perform their job functions. How you define the structure of your business environment directly impacts how access control applies to your users.
This section provides some background information about business environment structure. If your enterprise is large and complex, you can accurately reflect its structure as you set up your Siebel Business Applications. You can build multilevel hierarchies of organizations, divisions, and positions. You build a hierarchy by associating positions, for example, with other positions through parent-child relationships.
Defining your business environment structure involves setting up the elements shown in Table 24.
You can set up divisions, organizations, positions, responsibilities, and employees in any order. You can also associate these types of records with one another in a variety of ways. For example, to link a responsibility and an employee, you can associate the employee with the responsibility from the responsibility record, or you can associate the responsibility with the employee from the employee record.
CAUTION: Changing your company structure—such as positions and divisions—can cause Siebel Remote components (Transaction Router) to reevaluate access control for all objects related to the objects that have changed. This can result in diminished performance. For more information, see Siebel Remote and Replication Manager Administration Guide.
If your Siebel application is already deployed and you do not need to change your users' visibility (access), your company may not need more organizations. Some circumstances where your company could benefit from multiple organizations are as follows:
|Security Guide for Siebel Business Applications|