Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 2 removed)
  • 1633524340833-981.png
  • 1633524405853-995.png

Details

Page properties

Content

...	...	@@ -1,7 +1,7 @@
1	1
2	2
3	3	(% style="text-align: center;" %)
4		-= (% style="color:#2980b9; font-size:28px" %)**USER LEVEL SETUP**(%%) =
	4	+= (% style="font-size: 28px; color: rgb(41, 128, 185)" %)**USER LEVEL SETUP**(%%) =
5	5
6	6
7	7
...	...	@@ -15,7 +15,7 @@
15	15
16	16
17	17
18		-(% style="break-before: page; text-align: center;" %)
	18	+(% style="text-align: center;" %)
19	19	== (% style="color:#2980b9" %)**User Level setup**(%%) ==
20	20
21	21
...	...	@@ -22,8 +22,7 @@
22	22	An Administrator may wish to restrict/grant the system access of certain users based on their job function or expertise. The level of access per user group can be predefined in the system. This is known as a User Level. User Levels can only be set by the highest level granted, for example, the Super User. The Super User will select the Administration Menu on the top of the page and then select the (% style="color:#2980b9" %)“**User Levels**” (%%)option.
23	23
24	24
25		-(% style="text-align:center" %)
26		-[[image:1633524340833-981.png]]
	25	+[[image:User Level Setup_html_85c9f2f6850c9695.png||height="198" width="152"]]
27	27
28	28
29	29	The name of the User Level will be based on the Administrator’s requirements, except Super User which is a mandatory User Level and must not be changed or removed.
...	...	@@ -32,17 +32,18 @@
32	32	Insert the relevant line item with the corresponding Level. Level “1” always relates to the Super User level (the highest level granted, by default). All subsequent levels added should be consistent and should follow numerically thereafter.
33	33
34	34
35		-(% style="color:#2980b9" %)**NOTE: **(%%)The levels must follow a hierarchy. A Supervisor should not be on a lower level than an Administrator. It is (% style="color:#e74c3c" %)**VERY NB**(%%) to note that the “Level” determines functionality access. In the below example both Super User and Master User have Level 1, which is (% style="color:#e74c3c" %)problematic(%%). By granting Master User the same level as Super User, that level will now have access to all the functionality a Super User would have. Super User should always be Level 1 and all subsequent user levels must be level 2 up. Always remember that User types with the same level will automatically have the same access.
	34	+(% style="color:#2980b9" %)**NOTE: **(%%)The levels must follow a hierarchy. A Supervisor should not be on a lower level than an Administrator. It is (% style="color:#2980b9" %)**VERY NB**(%%) to note that the “Level” determines functionality access. In the below example both Super User and Master User have Level 1, which is problematic. By granting Master User the same level as Super User, that level will now have access to all the functionality a Super User would have. Super User should always be Level 1 and all subsequent user levels must be level 2 up. Always remember that User types with the same level will automatically have the same access.
36	36
37	37
38		-[[image:1633524405853-995.png]]
39	39
	38	+[[image:User Level Setup_html_6ca20014d6e74f.png||height="149" width="571"]]
40	40
	40	+
41	41	Once the User Level has been set up, you need to grant menu access to each level. Please refer to the manual “Granting Access to Menus”.
42	42
43	43
44	44
45		-(% style="break-before: page; text-align: center;" %)
	45	+(% style="text-align: center;" %)
46	46	== (% style="color:#2980b9" %)**Disclaimer and Copyright**(%%) ==
47	47
48	48

1633524340833-981.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.megank

Size

...	...	@@ -1,1 +1,0 @@
1		-31.8 KB

Content

1633524405853-995.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.megank

Size

...	...	@@ -1,1 +1,0 @@
1		-40.9 KB

Content