Setting Up a User Roles
DEFINITIONS:
A User Is a Quality Supervisor or Supervisor, the
...
person who completes an Assessment at a facility/provider
...
located in the
...
field.
Please note Quality Supervisor/Supervisor
...
operates at the Sub-National Level in the Org Unit and
...
is normally assigned between 20-50 facilities/providers.
Authorities refer to access privileges/permissions
User Groups refers to groups of the user such as End Users and Administrators
User refers to the End Users, in most cases the Quality Supervisor or Supervisor
Roles refer to access privileges such as access to DHIS2 applications, adding, editing and deleting objects.
Several DHIS2 Authorities are required in order to
...
interact with
...
H2 Metadata and Data. The
...
Authorities will grant the
...
Users permission to different DHIS2 configurations and features.
| Info |
|---|
Please Note: If you’re using the PCA |
...
(Program Configuration Application), the necessary User Roles |
...
are likely to already exist on the server, some of the User Roles are installed during the initial setup of the PCA, while others are installed as part of the HNQIS2 Metadata Package. |
For Data Capture (Web and Android App)
A User Role for Data Capture should include the following Authorities:
Web Data Capture | Android Data Capture |
|---|---|
|
...
|
|
...
Note: As of DHIS2 Android 2.6.2 a User does not require any authority to capture DHIS2 Tracker Data |
...
Program Administration
Program Administration requires several Authorities depending on the needs of the Administrator. All the recommended Authorities are listed below:
Metadata Authorities
Authority required to create or edit metadata objects in the DHIS2 server
...
*Denote:
The Public access should only be provided for analyses such as Dashbaord. Maps and Visualisation.
...
.
Metadata Object | Authority |
|---|---|
Dashboard (for H2 Metadata Generation) |
|
Data Element |
|
...
|
...
Add/Update Private
Legend Set |
|
...
| |
Map (for H2 Metadata Generation) |
|
Option Set |
|
...
| |
Program |
|
...
|
...
| |
Program Indicator |
|
...
|
...
Add/Update Private
| |
Program Rule |
|
...
| |
Program Stage |
|
...
|
...
Program Stage Section |
|
...
| |
Visualization (For H2 Metadata Generation) |
|
| Info |
|---|
Denote:* Avoid providing Public access to Program-related metadata, this function is reserved for HNQIS Administrators only. Public access should only be provided for analysis purposes such as Dashboard, Maps and Visualisation. |
Other Authorities
App access
...
Authority is required to administer H2
...
Programs on a DHIS2 server below is a list of options available.
App |
|
Tracker |
|
Import/Export |
|
System |
|
Please note
...
you may not need all of the
...
above Authorities as some are mainly used by the PCA features.
Assign User Roles
Assign Org Units for Data Capture and Data Analysis
Data Capture OUs (screenshot)
...
Web data capture
...
Android data capture
...
Data Capture OUs
...
You can either assign the individual Org Units (normally the facilities and/or providers) that will be evaluated by the supervisor or you can select the parent OUs (like province, district), which will automatically make available all facilities/providers in that district/province
You should always assign the specific providers/facilities that the supervisor will manage. Assigning the parent district/province will not work
...
Analytic OUs
...
You can select a provide, district or even the country, depending of the level of access that you want your user to have for analytics only.
...
This setting only affects analytics on the web, not in android.
...
Previous
Top
Next