module 05 users, positions and organizations

7/30/2019 Module 05 Users, Positions and Organizations

http://slidepdf.com/reader/full/module-05-users-positions-and-organizations 1/20

Users, Positions and Organizations 1 of 20

Siebel 8.0 Essentials



Module 5: Users, Positions and Organizations




Module Objectives

• To describe how data access can be controlled by users, positions

and organizations

• To implement the company structure using divisions, organizations,

positions, users and employees




Business Requirement

• Large-scale enterprise applications should selectively grant data to

users, for example:

–Sales Representatives should see their own region’s sales quota, but not of

other region’s

–Sales Managers should see all of their reports’ sales quota

• System Administrators require a mechanism to restrict access to datain an application




Solution: Access Control

• Siebel applications allow different users to view and access different

data, according to their user Id, position or organization in thecompany

–Data access control is independent of responsibilities and views

–Example: The two users, TARNOLD and CCHENG are accessing the same

view, but see different data in the view




Users

• Users are individuals who use the Siebel application

–Maybe employees, customers or partners

• A user requires a unique User ID and at least one responsibility to see

views in the application

• Multiple users can have the same name as long as their User IDs are

different


http://slidepdf.com/reader/full/module-05-users-positions-and-organizations 7/20Users, Positions and Organizations 7 of 20

Employees

• Employees are users who are employed by the company

–Employees are assigned to one or more positions –Each position belongs to one organization in the company



Positions

• Positions are used to control access to data within the application

–For example, sales representative is a position, and a sales representative’saccounts are visible only to members of his/her sales team

• Employees may have one or more positions

–One position is the primary position, the position a user assumes when

he/she logs in

–Employees only see data for their current position

–Employees can change their position after logging in



Changing Positions

• An employee can change position during a session

–From the application-level Tools menu, select User Profile Preferences >Change Position

• Changing the primary position for an employee is a job for the

administrator

Select Change

Position to change

position during a

session



Position Hierarchy

• Positions are arranged in a hierarchy

–Defines a reporting structure that allows managers to get data from direct/

indirect reports

–Navigate to Administration-Group > Positions to view the hierarchy

• Also shows primary user for each position

Pharma District

Manager can see

records of PharmaSales Rep 1 and

Pharma Sales Rep 2



Divisions and Organizations

• A company is divided into divisions, based on regions, business or

departments

• Divisions are arranged in a hierarchy

• An organization is a special type of division with which data is

associated



Positions and Divisions

• A position is assigned to one, and only one, division

• A position is associated with one, and only one, organization: theorganization to which the division belongs

Pharma District

Manager is assigned

to Xerco

Pharmaceuticals

division

The position belongs to

Xerco Pharmaceuticals

organization, the

organization to which the

division belongs



Implementing the Company Structure

1. Create Divisions and Division Hierarchy

2. Label some Divisions as Organizations

3. Create Positions

4. Create Employees

5. Create Users



Create Divisions and Division Hierarchy

• To create divisions, navigate to Administration-Group > Internal

Divisions view• Once divisions are created, they cannot be deleted



Label some Divisions as Organizations

• A division is labeled an organization by selecting the Organization Flag checkbox

• This cannot be undone

Organization Flag

check box



Create Positions

• To create positions, navigate to Administration-Group > Positions

view –Positions require a name and a division

• Some seed positions, like Siebel Administrator, are provided with

Siebel applications

• Best practice is to not delete positions, as they are related to data



Create Employees

• To create employees, navigate to Administration-User > Employees

view –Employee also appears as a user

• Every employee should have a first name, a last name, a user ID, a

position and an organization

• By default, the new employee records get the same organization as

the user creating the record

- Can be changed to reflect appropriate access control



Create Users

• Not all users are employees

–For example, customers and partners

• Create users in the Administration-User > Users view

• Customers and Partners require responsibilities but not positions



Module Highlights

• Users are individuals who log into the application.

–Require responsibilities

• Employees are users who are employed in the company

–Require at least one position

–Require to belong to at least one organization

• Positions are used to determine what data an employee can see

• A company is divided into a division hierarchy• Organizations are special divisions with which data is associated



Users Positions and Organizations 20 f 20

Lab

• In the lab you will:

–Implement a company structure, including divisions, organizations,positions, and employees

module 05 users, positions and organizations

Documents