A. Objective:

1. Some users should not be able to allocate a task to any other user. E.g customer using portal should be able to raise a request and create a task without seeing any other user in the system.

2. A user in helpdesk may want to assign a case to another user within their organisation.

3. A company administrator should be able to see all users in the company so support staff can work on any organisation.

4. The system administrator should be able to approve/disapprove any user in the system

based on the current design, the following rules should be applied. Using Link-HELPDESK as an example:

5. Alvis & Sanjay should have access to all users in the system because they have access to all 4 companies

6. Sanjeet should be able to see all users with access to company "LBS". No access to Philip and Sitla. Sanjeet can see Alvis because Alvis has access to company LBS.

7. A customer in company LBS should be able to view all users in their organisation

B. Design:

Add security below to achieve the above objectives.

1. Can view users in my organisation

2. Can view users that have access to my company

3. Can view all users in the system

PART A - Development work for this case has been completed.

1. The change will be available in version:12030.0201

2. The following changes were made(Include Database object names, Program classes and any other relevant information):

1. Added/Ammended the following new security options:
   1. Can view/manage all users in the system. To manage users assign access to Add/Edit/Delete.
   2. Can view/manage users in my Organisation. To manage users assign access to Add/Edit/Delete. Organisation is assigned in the "User Maintenance" form.
   3. Can view/manage users in my Primary company. To manage users assign access to Add/Edit/Delete. "Primary Company" is assigned in the "User Maintenance" form.
   4. Can view/manage users who have access to my "Logged In" company. To manage users assign access to Add/Edit/Delete.
2. The security options are self explanatory

3. Affected Areas:

1. User Access across the application especially Helpdesk

4. The issue was caused by:

1. Improve Security

5. Notes: 
6. Next Step: UAT

----------------------

PART B - Development Reference:

1. Changes implemented was according to the approved design (Y/N):

2. Variations to the approved design:

PART A - Development work for this case has been completed.

1. The change will be available in version:12.30.0204

2. The following changes were made(Include Database object names, Program classes and any other relevant information):

1. Changed the user list to show all users in the same organisation when the user has view access to organisations.

3. Affected Areas:

1. User List

4. The issue was caused by:

5. Notes: Refer to the scenario below: Alvis has access to view users in my organisation.

1. When Alvis logs into company INFO, he will see users: Alvis, Sanjay in menu "user maintenance"
2. When Alvis logs into company EBS, he will see users: Alvis, Rashna menu "user maintenance"

6. Next Step: 

----------------------

PART B - Development Reference:

1. Changes implemented was according to the approved design (Y/N):

2. Variations to the approved design:

PART A - Development work for this case has been completed.

1. The change will be available in version:12.30.0205

2. The following changes were made(Include Database object names, Program classes and any other relevant information):

1. The changes were not included in build 12.30.0204.

3. Affected Areas:

4. The issue was caused by:

5. Notes: 
6. Next Step: UAT

----------------------

PART B - Development Reference:

1. Changes implemented was according to the approved design (Y/N):

2. Variations to the approved design: