Changes for page Role Creation

Last modified by karimpirani on 2014/07/03 14:26
From version Icon 10.1 Icon
edited by sghareeb
on 2014/06/24 18:26
Change comment: There is no comment for this version
To version Icon 12.1 Icon
edited by karimpirani
on 2014/06/27 11:56
Change comment: There is no comment for this version

Summary

Details

Icon Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.sghareeb
1 +XWiki.karimpirani
Content
... ... @@ -1,6 +1,6 @@
1 -(% style="font-size: 13.63636302947998px; background-color: rgb(245, 245, 245);" %)The first step of the SMR startup process is to define user roles. User roles are essentially combinations of permissions to perform particular tasks within the system. These roles will reflect specific groups of people in your organization and their functions. When you create specific users in the system, you will be assigning these users to a particular role.
1 +The first step of the SMR startup process is to define user roles. User roles are essentially combinations of permissions to perform particular tasks within the system. These roles will reflect specific groups of people in your organization and their functions. When you create specific users in the system, you will be assigning these users to a particular role.
2 2  
3 -(% style="font-size: 13.63636302947998px; background-color: rgb(245, 245, 245);" %)For example, an administrator is obviously a role for someone who has a wide range of permissions. More operational roles will be important as well: Supervisor, Case Manager, Clinician, Data Management Specialist. Each of these will have a different set of abilities in the system given their jobs. For example, a CaseManager will not be able to approve a CANS whereas a Supervisor would have that permission.
3 +For example, an administrator is obviously a role for someone who has a wide range of permissions. More operational roles will be important as well: Supervisor, Case Manager, Clinician, Data Management Specialist. Each of these will have a different set of abilities in the system given their jobs. For example, a CaseManager will not be able to approve a CANS whereas a Supervisor would have that permission.
4 4  
5 5  There are two primary tasks in this process:
6 6  
... ... @@ -12,7 +12,7 @@
12 12  ~1. In the Administration Menu, click on the "Roles..." option, as shown below.
13 13  
14 14  
15 -[[image:Admin - Roles Menu.png||width="100%"]]
15 +[[image:Admin - Roles Menu.png||width="70%"]]
16 16  
17 17  
18 18  1.1 This will display the screen shown below. The list of roles set up on the system with the standard selection buttons and filtering capabilities.
... ... @@ -27,7 +27,7 @@
27 27  
28 28  Then the Permissions need to be assigned to each Role.
29 29  
30 -(% style="font-size: 13.63636302947998px; background-color: rgb(245, 245, 245);" %)The screenshot below shows the the Clinician Role and some examples of possible assigned permissions.
30 +The screenshot below shows the the Clinician Role and some examples of possible assigned permissions.
31 31  
32 32  [[image:Admin - Add Role - Clinician.png||width="100%"]]
33 33  
... ... @@ -53,10 +53,7 @@
53 53  
54 54  3.4 Click on the Save button
55 55  
56 - I 3
57 57  
58 -(% style="font-size: 13.63636302947998px; background-color: rgb(245, 245, 245);" %)
59 -
60 60  
61 61  
62 62  4. Associate functional permissions for this role using the Assigned Permissions area. [[What are functional permissions>>doc:Functional Permissions]]?
... ... @@ -67,9 +67,7 @@
67 67  
68 68  4.3 Similarly, to remove a permission, click on the item in the right pane and then click on "Remove Selected"
69 69  
70 -I 4
71 71  
72 -
73 73  
74 74  5. Click on the Save button to save this information.
75 75