How do you give districts access to their own WASH data?

Create one organization with a branch per district, then grant permissions to the branch rather than to individual people. Adding a district officer to their branch gives them access to that district's surveys, deployments and dashboards, and to nothing from other districts.

Video: Organizations in mWater on YouTube

Why this matters

A national WASH information system fails in practice when every new district officer means an administrator hand-editing permissions on dozens of surveys, deployments and dashboards. Districts then either wait weeks for access or get blanket access to the whole country's data. Branch-based permissions solve the underlying management problem: responsibility for a district's data sits with that district, while the ministry keeps oversight of everything below it in the hierarchy.

How to do it

  1. Go to Manage > Organizations and create an organization for the ministry or programme, or open the one you already have.
  2. Hover over an existing branch and choose "+ Add Branch" to build the hierarchy you actually work in, commonly national, then region or province, then district.
  3. Click into a district branch and add people to its groups. Admins can manage the branch, Managers and Viewers are added automatically to deployments made from that branch, and user-defined Teams are useful for enumerators.
  4. On each survey, deployment, dashboard or datagrid, grant permission to the branch or team instead of to named individuals.
  5. Remember that permissions given at the top branch flow downward, so a national viewer sees every district, while permissions on a sibling branch do not flow across.
  6. When someone changes post, add or remove them in the branch's Users tab. Their access to every connected survey and dashboard follows automatically.

Go deeper