DEFINITIONS:
Authorities refers to access priviliges privileges
User Groups refers to groups of user such as End Users and Administrators
User refers to the End Users in most cases the Quality Supervisor or Supervisor
Roles refers to access privileges such as access to DHIS2 applications, adding, editing and deleting objects.
Object refers to programs, data elements, option sets and other configurable elements within DHIS2
...
In order to keep DHIS2 as clean and organised as possible, User Groups and Roles should be defined to limit access to the features available in DHIS2.
User Roles
Several DHIS2 Authorities are required in order to be able to interact with the H2 Metadata and Data. The authorities will grant the users permission to different DHIS2 configurations and features .
...
Please Note
...
available
...
For Data Capture (Web and Android App)
A User Role for Data Capture should include the following Authorities:
...
Web Data Capture
...
Android Data Capture
...
Apps:
Browser Cache Cleaner App
Dashboard App
Tracker Capture App
Tracker:
Uncomplete events
View event analytics
...
Tracker:
Uncomplete events
Note: As of DHIS2 Android 2.6.2 a User does not require any authority to capture DHIS2 Tracker Data
For 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 edit metadata objects in the DHIS2 server.
| Info |
|---|
*Denote: The Public access should only be provided for analyses such as Dashbaord. Maps and Visualisation. Avoid providing Public access for Program-related Metadate, this function is reserved for HNQIS Administrators only. |
...
Metadata Object
...
Authority
...
Dashboard (for H2 Metadata Generation)
...
Add/Update Public
Add/Update Private
...
Data Element
...
Add/Update Public*
Add/Update Private
...
Legend Set
...
Add/Update Public*
Add/Update Private
...
Map (for H2 Metadata Generation)
...
Add/Update Public
Add/Update Private
...
Option Set
...
Add/Update Public*
Add/Update Private
...
Program
...
Add/Update Public*
Add/Update Private
Delete
...
Program Indicator
...
Add/Update Public*
Add/Update Private
Delete
...
Program Rule
...
Add/Update Public*
Delete
...
Program Stage
...
Add/Update Public*
Delete
...
ProgramStageSection
...
Add/Update Public*
Delete
...
Visualization (For H2 Metadata Generation)
...
Add/Update Public
Add/Update Private
Delete
Other Authorities
App access authority is required to administer H2 programs in a DHIS2 server.
...
App
...
Browser Cache Cleaner App
Dashboard App
Datastore App (Required if using Program Config App)
Maintenance App
Tracker Capture App (To check configurations)
Program Config App (Recommended)
...
Tracker
...
Manage program rule
...
Import/Export
...
Export metadata (Required if using Program Config App)
Import metadata (Required if using Program Config App)
...
System
...
View User (To assign Sharing Settings to other users)
...
DHIS2
...
User Groups in H2 are used to define the users that will be able to perform maintenance to the different H2 Programs (referred to as Admins) and the users that will be able to interact with said Programs (referred to simply as Users).
By default, the HNQIS2 Metadata Package includes two User Groups that can be used as templates for other groups: HNQIS2 - Admins and HNQIS2- Users.
| Info |
|---|
Please Note If you’re using the PCA, the HNQIS2 Metadata Package (that also includes the base User Groups) can be installed/updated easily. |
It is recommended to that a pair of Groups for Admins and Users is created for each use case. For instance, it is a common practice to separate Checklists by country, meaning that a group of three countries: Kenya, Zimbabwe and Angola; should have the following sets of User Groups:
...
Kenya (KE)
...
Zimbabwe (ZW)
...
Angola (AO)
...
KE HNIQS2 - Admins
KE HNQIS2 - Users
...
ZW HNIQS2 - Admins
ZW HNQIS2 - Users
...
AO HNIQS2 - Admins
AO HNQIS2 - Users
If your server includes a multi-country setup, it is a good practice to include the ISO code of the country as a prefix for each User Group.
After the User Groups are created, the Sharing Settings of the H2 Programs should include a configuration as follows:
...
User Group
...
Metadata Settings
...
Data Capture Settings
...
Admins
...
Can Edit and View
...
Can Capture and View
...
Users
...
Can View only
...
Can Capture and View
Not all of the authorities listed above are required, some are mainly used by the PCA features.