Developing and Deploying Siebel Business Applications > Installing Software, Adding Users, and Creating the Company Structure > Process of Adding Users >

Creating Responsibilities

This task is a step in Process of Adding Users.

A responsibility determines the views a user can access. For example, the Siebel Administrator responsibility allows the user to access all views. Creating responsibilities lets you limit user access to views. If you do not use a predefined responsibility, then you must create a new one.

In this topic, you create responsibilities for NREC employees and partners. You do not create a responsibility for the developer. To perform development tasks, the developer typically must access all views. The predefined Siebel Administrator responsibility provides access to all views. You assign the Siebel Administrator responsibility to the developer.

To create responsibilities

1. Log in to the Partner Manager application as an administrator.

   For more information, see Logging In as the Siebel Administrator.

2. Navigate to the Administration - Application screen, and then choose Responsibilities.
3. Create a responsibility for the NREC CEO:
   1. In the Responsibilities list, click Query, enter CEO in the Responsibility field, and then click Go.

      You cannot edit a predefined responsibility. You must copy it and then modify it. The CEO predefined responsibility includes most views that the NREC CEO requires. The NREC CEO responsibility must access all views except application administration views.

   2. Click Menu and then choose the Copy Record menu item.

      Siebel CRM creates a new responsibility. It copies the views from the predefined responsibility, but it does not copy the users from the predefined responsibility.

   3. Enter values using information from the following table.

      Field	Value
      Responsibility	NREC CEO
      Description	Leave empty

4. Create a responsibility for the NREC Sales Manager:
   1. In the Responsibilities list, click Query, enter Sales Manager in the Responsibility field, and then click Go.
   2. Click Menu and then choose the Copy Record menu item.
   3. Enter values using information from the following table.

      Field	Value
      Responsibility	NREC Sales Manager
      Description	Leave empty

5. Create a responsibility for the NREC Agent:
   1. In the Responsibilities list, click Query, enter Universal Agent in the Responsibility field, and then click Go.

      The predefined Universal Agent responsibility contains many of the views that the NREC Agent requires. In an actual development project, you must customize the views that each responsibility can access.

   2. Click Menu and then choose the Copy Record menu item.
   3. Enter values using information from the following table.

      Field	Value
      Responsibility	NREC Agent
      Description	Leave empty

6. Create a responsibility for the NREC Partner Agent:
   1. In the Responsibilities list, click Query, enter Partner Sales Rep in the Responsibility field, and then click Go.
   2. Click Menu and then choose the Copy Record menu item.
   3. Enter values using information from the following table.

      Field	Value
      Responsibility	NREC Partner Agent
      Description	Leave empty

Guidelines for Creating a Responsibility

If you create a responsibility, then it is recommended that you use the following guidelines:

• Define each responsibility to correspond to a major job function in your organization. For example, you might create a separate responsibility for each of the following job functions:
  • NREC CEO
  • Sales manager
  • Partner manager
  • Field sales representatives
• Copy a predefined responsibility and then customize it. Note that you cannot edit a sample responsibility.
• For a developer, add new views to the administrator responsibility. The administrator responsibility provides access to all views. A developer typically helps troubleshoot the Siebel application and requires access to all views.
• Do not provide end users with access to the following views and screens:
  • System Preferences view. This view controls server logic and processing. Provide access to the System Preferences to only a particular group of administrators.
  • Administration - Applications screens.
  • Employees, Master Forecasts, Mobile Clients, Responsibilities, Views, and Territories screens. These screens can affect the entire application.
  • License key view. To discourage an unauthorized user from attempting to change a license key, you can limit access to the license key view. To do this, you use the License Keys view in the Administration - Applications screen. To hide the license key view, disable the Siebel License Key view in the responsibility for the user.