User:Ras26585/sandbox

Document Details

Name	Version Number	Module	Sub Module Modification in Multiple User Account Privileges	1.0	Web	>Utility > Multiple User Account

Action Taken (add/del/change)	Previous page number	New page number	Revision description

Revision Details

Action Taken (add/del/change)	Previous page number	New page number	Revision description

These are confidential documents. Unauthorized access or copying is prohibited.

Approved by:						Authorized by:

Date:							Date:

Contents

1.	Introduction	3 1.1	Scope	3 1.2	Definitions & Acronyms	3 1.3	References	3 2.	General Description	3 2.1	Product Functions	3 2.2	Constraints	5 2.3	User Interface	5 2.4	Assumptions & Validations	6 2.5	Communication	6 2.6	Module Affected	6 2.7	Performance Requirements	6 2.8	Additional comments	6 2.9	Future requirements	6 3.	Change Management Process	7 4.	Projections	7

1.	Introduction

1.1	Scope

There is facility provided on our website for buyer’s partner/subordinate/broker by giving rights as per buyer’s choice. Few more fields/pages are required to be added in it.

1.2	Definitions & Acronyms

Word	Definition Parent login / Parent user	Main user (buyer) to whom we have given access of our website. Child login / Child user	Buyer’s subordinate to whom buyer has given access of using his account on our website.

1.3	References

Title	Modification in Multiple User Account Privileges VCS IDN. 300 Version No.	1 Module / Departments	Web Sub Module	Multiple User account page System suggested by	As per buyer Request Prepared By	Document Team Developer Date	23-July-2013

2.	General Description

2.1	Product Functions

2.1.1	New username creation Below mentioned fields are required to be added / modified for new username creation.

Field name	Mouse over	Field type	Field values	Description Name	Name of the user whom you want to give access	Textbox	User Input	User (Buyer) will type the name of his subordinate whom he would like to give the access of his web account Username	Define username			User will insert the username; system will refer login creation policy. Password	Define Password			User will insert the password; system will refer login creation policy. Re-enter password	Confirm Password			User will confirm the password; system will refer login creation policy. Stock Pages	Access to stock pages	Checkbox PDS	Should get rights of PDS page Look & Bid	Should get rights of L&B page Other Stock page	Should get rights of all other pages than PDS and L&B Actions Allowed	Access to perform these actions		View only	Should only view the stock, should now allowed performing any action. Quote	Should view and allowed to quote Buy	Should allowed to view, quote & buy Show price	Display Price of the diamond	Radio Button	Yes	Price should display No	Price should not be displayed Quotelist	Access to my Quotelist		Yes	Particular section should be allowed to child user if selected ‘Yes’, in case of ‘No’ it should not allowed. No Watchlist	Access to my Watchlist		Yes No Accounts	Access to my Invoices & Ledger details		Yes No Current Purchase	Access to my Purchases		Yes No Current Summary	Access to my Selections and summery Details		Yes No Track	Access to my Reservations/ memo		Yes No My Request	Access on request made for physical inspection		Yes No Personal Profile	View / Edit my Profile		Yes No Save	N.A. Action Button	N.A.	New username will be created Clear All				All field values already inserted by user will be cleared

Note:

If Buy or Quote option is selected than Show price should be set to yes.

2.1.2	Modify / Delete existing username(s) Once username is created, buyer can modify / Delete the same. Apart from password & re-enter password all above fields of new username creation should come here. In addition to that below mentioned fields are required to be added.

Field name	Mouse over	Field type	Field values	Description Select	N.A.	Radio button	Names & usernames	It will show all already created child Names & usernames Delete			N.A. It will delete selected username which was created by user.

Note:

Already given access should be shown over here and (Parent) user can modify the same.

2.2	Constraints N. A.

2.3	User Interface

2.3.1	New username creation Please click here to view the design of the page.

2.3.2	Modify / Delete existing username(s) Please click here to view the design of the page.

2.4	Assumptions & Validations

Validations:

2.4.1	Login policy should apply for all child users. 2.4.2	Maximum 5 child logins should be allowed. 2.4.3	Once child user logins, in his welcome page, he will see his username. 2.4.4	Access management policy should apply. (Below will be covered in it). On welcome page, we are showing below account details o My purchase (Current purchase) o My Quotelist o My Request o My Watchlist If child user is not having access of above, then it should not be displayed on welcome page, if all things are not accessed then account detail tab should not be displayed on the page. 2.4.5	Care has to be taken regarding parent child privileges i.e. if a parent has only viewing rights than he cannot issue buying rights to his child account. 2.4.6	Child user will not have access of this (multiple user creation) page. 2.4.7	Login Deactivation policy should apply.

2.5	Communication N. A.

2.6	Module Affected

Pls click here to see the details of modules & sub modules affected.

2.7	Performance Requirements N. A.

2.8	Additional comments N. A.

2.9	Future requirements Right now these fields are independent but in future we might link them. For e.g. if we linked Quote & Buy option, then if parent user give access of Buy to child then by default child will get access of Buy & Quote both. 3.	Change Management Process N. A. 4.	Projections N. A.