dhis2-devs team mailing list archive
-
dhis2-devs team
-
Mailing list archive
-
Message #21591
[Branch ~dhis2-documenters/dhis2/dhis2-docbook-docs] Rev 694: Minor
------------------------------------------------------------
revno: 694
committer: Lars Helge Øverland <larshelge@xxxxxxxxx>
branch nick: dhis2-docbook-docs
timestamp: Fri 2013-03-15 15:34:05 +0100
message:
Minor
modified:
src/docbkx/en/dhis2_user_man_sharing.xml
--
lp:~dhis2-documenters/dhis2/dhis2-docbook-docs
https://code.launchpad.net/~dhis2-documenters/dhis2/dhis2-docbook-docs
Your team DHIS 2 developers is subscribed to branch lp:~dhis2-documenters/dhis2/dhis2-docbook-docs.
To unsubscribe from this branch go to https://code.launchpad.net/~dhis2-documenters/dhis2/dhis2-docbook-docs/+edit-subscription
=== modified file 'src/docbkx/en/dhis2_user_man_sharing.xml'
--- src/docbkx/en/dhis2_user_man_sharing.xml 2013-03-14 11:17:58 +0000
+++ src/docbkx/en/dhis2_user_man_sharing.xml 2013-03-15 14:34:05 +0000
@@ -87,14 +87,16 @@
reports could be viewed and maintained by the country and global personell, without being
visible or impacting the system for other countries in the organisation.</para>
<para>A similar approach could work for a scenario with a donor, multiple funding agencies and
- implemeting partners in a country, where user groups could be set up for each of those
- entities.</para>
+ implementing partners in a country, where user groups could be set up for each of those
+ entities. That way each implementing partners could create and share their reports internally
+ within their organisation without affecting or allowing access to others. Reports could also
+ be shared with supervisors and funding agencies at the end of reporting periods.</para>
<para>Another use-case is a country department of health with multiple health programs.
Typically there is a need for having general reports and charts for the department while
- allowing the health programs to develop specific reports and charts for internal. This can be
- achieved by creating user groups for each health program. Later, when developing reports and
- charts, these can be made viewable and editable to the program user group only. This way the
- reports will not be visible to other programs and users. This is benecifial because the
+ allowing the health programs to develop specific reports and charts for internal use. This can
+ be achieved by creating user groups for each health program. Later, when developing reports
+ and charts, these can be made viewable and editable to the program user group only. This way
+ the reports will not be visible to other programs and users. This is benecifial because the
reports are kept internal to the program and because the visible list of reports of other
users are kept shorter and more relevant.</para>
</section>