Versions Compared

Old Version 1

changes.mady.by.user Shrab Sahota (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user Shrab Sahota (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

  • Apps:

    • Browser Cache Cleaner App

    • Dashboard App

    • Tracker Capture App

  • Tracker:

    • Incomplete events

    • View event analytics

  • Tracker:

    • Incomplete events

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.

Metadata Object

Authority

Dashboard (for H2 Metadata Generation)

  • Add/Update Public

  • Add/Update Private

Data Element

  • 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 Private*

  • Delete

Program Indicator

  • Add/Update Private*

  • Delete

Program Rule

  • Add/Update Public

  • Delete

Program Stage

  • Add/Update Public

  • Delete

Program Stage Section

  • Add/Update Public

  • Delete

Visualization (For H2 Metadata Generation)

  • Add/Update Public

  • Add/Update Private

  • Delete

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

  • 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)

Please note you may not need all of the above Authorities as some are mainly used by the PCA features.

Previous

Top

Next