The document provides guidelines for managing user accounts and roles within an administrative system, emphasizing the careful creation and editing of users and their access permissions. It details the protocols for document handling, including onboarding processes, document templates, and email communications with clients. Additionally, it highlights the role-based access control for users, particularly for the 'fuimp' category, which allows them to create but not edit client documents.

1. Admin Part:
User List:
Create User:
Note:Here language androle isa importantthingcause whenthe newlycreateduserloggedinthis
systemhe will findeverythingonhislocal whichadminassignedonthe time of hiscreation.Which
menuhe able to accessit alsodependentonhisrole .soneedtobe careful whenwe create anewuser.

2. EditUser:
At the time of edita userinformationbe careful tofill the passwordcorrectlyandalsoyoucan’tput
themblank.soafterupdate auseryou have to notifyabouthisnew password.
Menu Access:

3. Menu AccessOperation:

4. Functional BlockList:
Have to be notedthatthisblockhave to be done fora user notrole.bydefaultall userhave accesson
hisaccessedmenusactionbutif you wantto blocka action forthemthenyou have to checkedthe
expectedblockedactionfromthisUI.
Role:
Note: You have to mentioned “code role hierarchy”if you wantdefine hisparentsrole.

5. DocumentFieldType:
If you wantto sync thisfieldvalue withclientdetailsinformationthenyouhave keepit(“Description
documentfieldtype”) same asdatabase fieldname onclienttable .Label isshownondocumentform.
Data type will be the type of value .
If you wantto translate the labelsthenyoumustaddlocal and translatedlabel tothislocal button.By
defaultlabel will be shown.

6. You can alsoeditthose translationsfromhere.
DocumentType:

7. DocumentType List:
NewContentmodel:

8. DocumentEdit:

9. DocumentTemplate:
Template listbyLocal
For creating newtemplate Inalocal,

10. ClientList:
Adminlevel userwill abletosee all userwhose hierarchyparentishe.
Create Client:

11. OnboardingDocumenttype:
For creatingonboardingdocument,

13. KYC:SelectKYCfromhere andgenerate document

14. OnboardingDocumentList
Documentvalue edit

15. EditForm:

16. Editthis documentTemplate:
Template Edit:
KYC Mail:
If you wantto sendthe documentdata edittoclientviamail thenclickhere andsenda mail.

18. Aftersendmail youwill findnewbuttonresendmail optionondocument.
Clientwill seethe mail:

19. Nowclickingthe link clientable topersonal informationabouthiscompany

20. Aftersubmit
Thislinkisonlyone time accessible withtoken.If thisclienttrytoaccesstwice thenhe found
Othersdocumentissame like this.
Transaction:
Firstneedto create a transaction

21. Create Form:
Transactionlist:

22. Here all transactionrelateddocumenttype isavailable

23. Suppose appel de prime:
Otherthingsare same like onboardingdocumenttype.

24. List of all documents:
Able tosee all documentsof hisclient

25. FUIMP Part:
The access listof FUIMP fullycontrolledbyAdmin.Admincanon/ off anyaction of a specificuser.
FUIMP can create client:
He able tosee onlyhisclientsonhislist.

26. He have accessto create documentbutnot have permissiontoeditthe createdvalue andtemplateof
hisdocuments.Butable to see all documentsof hisclients.
Same access fortransactionrelateddocuments.
For creatingonboardingdocument,

28. KYC:SelectKYCfromhere andgenerate document

29. KYC Mail:
If you wantto sendthe documentdata edittoclientviamail thenclickhere andsenda mail.
Aftersendmail youwill findnewbuttonresendmail optionondocument.

30. Clientwill seethe mail:
Nowclickingthe link client able topersonal informationabouthiscompany

31. Aftersubmit
Thislinkisonlyone time accessible withtoken.If thisclienttrytoaccesstwice thenhe found
Othersdocumentissame like this.
Transaction:
Firstneedto create a transaction
Create Form:

32. Transactionlist:

33. Here all transactionrelateddocumenttype isavailable

34. Suppose appel de prime:

35. List of alldocuments:
Able tosee all documentsof hisclient