dhis2-users team mailing list archive

[Pamod Amarakoon <pamodm@xxxxxxxxx>]

I'd really like to see sharing is implemented on program stages. We also
have a similar requirement where user access is needed to be controlled on
program stage basis.

On Mon, Aug 15, 2016 at 7:20 AM, Prosper BT <ptb3000@xxxxxxxxx> wrote:

> Dear Elmarie,
>
> Are the other users assigned to these orgunits supposed to access some
> parts of this tracker program?
>
> If yes, then design the program and use user roles to restrict access,
> create a user role and assign the program to it and that user role should
> be only assigned to the users supposed to view the program.
>
> If No, and want some users to see some parts or stages and not the others,
> its not yet supported - sharing program stages.
>
> Regards
>
>
>
> On Mon, Aug 15, 2016 at 7:02 AM, Elmarie Claasen <elmarie@xxxxxxxx> wrote:
>
>> Hi all,
>>
>>
>>
>> I have a use case where I need to create a tracker program to capture
>> meeting resolutions of a sensitive/confidential nature. Each of these
>> resolutions should be shared with particular users attached to a specific
>> organisation unit for action but not with other users attached to the same
>> organisation unit.
>>
>> Is this currently possible to share TEIs only with selected users or is
>> it possible to add this?
>>
>>
>>
>> Regards,
>>
>>
>>
>> *Elmarie Claasen*
>>
>> [image: Hisp logo]
>>
>> Project Manager
>>
>> Health Information Systems Program
>>
>> Tel:      041-367 1027
>>
>> Cell:     082 374 2209
>>
>> E-mail: elmarie@xxxxxxxx
>>
>> Skype:  elmarie.claasen52
>>
>>
>>
>>
>>
>> This message and any attachments are subject to a disclaimer published at
>> http://www.hisp.org/policies.html#comms_disclaimer .   Please read the
>> disclaimer before opening any attachment or taking any other action in
>> terms of this electronic transmission.
>> If you cannot access the disclaimer, kindly send an email to disclaimer@xxxxxxxx
>> and a copy will be provided to you. By replying to this e-mail or opening
>> any attachment you agree to be bound by the provisions of the disclaimer.
>>
>>
>>
>> *This message and any attachments are subject to a disclaimer published
>> at http://www.hisp.org/policies.html#comms_disclaimer
>> <http://www.hisp.org/policies.html#comms_disclaimer>.  Please read the
>> disclaimer before opening any attachment or taking any other action in
>> terms of this electronic transmission.  If you cannot access the
>> disclaimer, kindly send an email to disclaimer@xxxxxxxx
>> <disclaimer@xxxxxxxx> and a copy will be provided to you. By replying to
>> this e-mail or opening any attachment you agree to be bound by the
>> provisions of the disclaimer.*
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-users
>> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dhis2-users
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> Prosper Behumbiize, MPH
> Global DHIS2 Implementation| HISP Uganda/University Of Oslo
> +256 752 751 776 | +256 776 139 139
> prosper@xxxxxxxxxxxxxx <ptb3000@xxxxxxxxx> | prosper@xxxxxxxxx | Skype:
> prospertb
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Regards,
Pamod Amarakoon

Confidentiality Notice: the information contained in this email and any
attachments may be legally privileged and confidential. If you are not an
intended recipient, you are hereby notified that any dissemination,
distribution, or copying of this e-mail is strictly prohibited. If you have
received this e-mail in error, please notify the sender and permanently
delete the e-mail and any attachments immediately. You should not retain,
copy or use this e-mail or any attachments for any purpose, nor disclose
all or any part of the contents to any other person.