We have an instance with an Event program and a user role called “Data Capturer - Events” with the following authorisations - but one or more is missing:
Add/Update event
Add/Update Tracked Entity
Add/Update Tracked Entity Data Value
Delete Data Value
Generate Min-Max Value
Run validation
See Browser Cache Cleaner module
See Dashboard Intergration Module
See even Capture Module
See Event Report Module
See Event Visualiser module
See GIS Module
See Pivot table module
See report module
See validation rule
Something is missing, though - when a data capturer opens the Event Capture app and selects an orgunit with a number of pre-existing events, nothing is showing. Also when selecting “Register event”, all the drop-down option sets with a large number of options are blank.
If I add ALL to the user role, or if I add all the individual authorisations, everything works fine.
Two questions:
Can anybody see which authorisation(s) is/are missing in the list above?
Where can I find an overview of all authorisations in the system with a detailed explanation of (a) what exactly that authorisation provides access to and (b) what authorisations have an impact on which areas (routine data capture/use, event data capture/use, tracker data capture/use).
Small correction: we have now ascertained that if the Data Capturer - Events have every single authorisation selected (except ALL), it does NOT work. If we on the other hand select ALL, then it works.
What is the difference between ALL and the sum of all individual authorisations?
We have an instance with an Event program and a user role called “Data Capturer - Events” with the following authorisations - but one or more is missing:
Add/Update event
Add/Update Tracked Entity
Add/Update Tracked Entity Data Value
Delete Data Value
Generate Min-Max Value
Run validation
See Browser Cache Cleaner module
See Dashboard Intergration Module
See even Capture Module
See Event Report Module
See Event Visualiser module
See GIS Module
See Pivot table module
See report module
See validation rule
Something is missing, though - when a data capturer opens the Event Capture app and selects an orgunit with a number of pre-existing events, nothing is showing. Also when selecting “Register event”, all the drop-down option sets with a large number of options are blank.
If I add ALL to the user role, or if I add all the individual authorisations, everything works fine.
Two questions:
Can anybody see which authorisation(s) is/are missing in the list above?
Where can I find an overview of all authorisations in the system with a detailed explanation of (a) what exactly that authorisation provides access to and (b) what authorisations have an impact on which areas (routine data capture/use, event data capture/use, tracker data capture/use).
Have you added the event program to the role. The ALL authority is not a summation of all other permissions but a special designation that provides access to grant access to all apps and privately created objects (with the exception of dashboards).
We have an instance with an Event program and a user role called “Data Capturer - Events” with the following authorisations - but one or more is missing:
Add/Update event
Add/Update Tracked Entity
Add/Update Tracked Entity Data Value
Delete Data Value
Generate Min-Max Value
Run validation
See Browser Cache Cleaner module
See Dashboard Intergration Module
See even Capture Module
See Event Report Module
See Event Visualiser module
See GIS Module
See Pivot table module
See report module
See validation rule
Something is missing, though - when a data capturer opens the Event Capture app and selects an orgunit with a number of pre-existing events, nothing is showing. Also when selecting “Register event”, all the drop-down option sets with a large number of options are blank.
If I add ALL to the user role, or if I add all the individual authorisations, everything works fine.
Two questions:
Can anybody see which authorisation(s) is/are missing in the list above?
Where can I find an overview of all authorisations in the system with a detailed explanation of (a) what exactly that authorisation provides access to and (b) what authorisations have an impact on which areas (routine data capture/use, event data capture/use, tracker data capture/use).
YES, the program is added to the role, and its sharing is set to public view and edit (with login).
We have found earlier dev threads about very similar problems, but all indications are that those were fixed in 2.21. We have tested the latest 2.22 and the latest 2.23 - no difference. The only way to make it work is either to include ALL with that user role, or else log in as superuser. All other authorisations do not work.
Regards
Calle
···
On 6 July 2016 at 15:07, Busoye Anifalaje busoye@hisp.org wrote:
Hi Calle,
Have you added the event program to the role. The ALL authority is not a summation of all other permissions but a special designation that provides access to grant access to all apps and privately created objects (with the exception of dashboards).
Small correction: we have now ascertained that if the Data Capturer - Events have every single authorisation selected (except ALL), it does NOT work. If we on the other hand select ALL, then it works.
What is the difference between ALL and the sum of all individual authorisations?
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@hisp.org 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.
We have an instance with an Event program and a user role called “Data Capturer - Events” with the following authorisations - but one or more is missing:
Add/Update event
Add/Update Tracked Entity
Add/Update Tracked Entity Data Value
Delete Data Value
Generate Min-Max Value
Run validation
See Browser Cache Cleaner module
See Dashboard Intergration Module
See even Capture Module
See Event Report Module
See Event Visualiser module
See GIS Module
See Pivot table module
See report module
See validation rule
Something is missing, though - when a data capturer opens the Event Capture app and selects an orgunit with a number of pre-existing events, nothing is showing. Also when selecting “Register event”, all the drop-down option sets with a large number of options are blank.
If I add ALL to the user role, or if I add all the individual authorisations, everything works fine.
Two questions:
Can anybody see which authorisation(s) is/are missing in the list above?
Where can I find an overview of all authorisations in the system with a detailed explanation of (a) what exactly that authorisation provides access to and (b) what authorisations have an impact on which areas (routine data capture/use, event data capture/use, tracker data capture/use).
Checked the permissions you set. Not sure but can you try adding Add/Update Tracked Entity Instance. Strictly speaking an event does not have an entity but each record might be conceived as an instance. Worth trying I think. If it works then you want to also add Delete Tracked Entity Instance.
YES, the program is added to the role, and its sharing is set to public view and edit (with login).
We have found earlier dev threads about very similar problems, but all indications are that those were fixed in 2.21. We have tested the latest 2.22 and the latest 2.23 - no difference. The only way to make it work is either to include ALL with that user role, or else log in as superuser. All other authorisations do not work.
Regards
Calle
Busoye Anifalaje (PhD)
Director of Services (Principal), BAO Systems
UK: +44 7901-740-757 | US: +1 682-307-0986| busoye@baosystems.com | http://www.baosystems.com |
Skype: busoye | 2900 K Street, Suite 404, Washington D.C. 20007
On 6 July 2016 at 15:07, Busoye Anifalaje busoye@hisp.org wrote:
Hi Calle,
Have you added the event program to the role. The ALL authority is not a summation of all other permissions but a special designation that provides access to grant access to all apps and privately created objects (with the exception of dashboards).
Small correction: we have now ascertained that if the Data Capturer - Events have every single authorisation selected (except ALL), it does NOT work. If we on the other hand select ALL, then it works.
What is the difference between ALL and the sum of all individual authorisations?
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@hisp.org 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.
We have an instance with an Event program and a user role called “Data Capturer - Events” with the following authorisations - but one or more is missing:
Add/Update event
Add/Update Tracked Entity
Add/Update Tracked Entity Data Value
Delete Data Value
Generate Min-Max Value
Run validation
See Browser Cache Cleaner module
See Dashboard Intergration Module
See even Capture Module
See Event Report Module
See Event Visualiser module
See GIS Module
See Pivot table module
See report module
See validation rule
Something is missing, though - when a data capturer opens the Event Capture app and selects an orgunit with a number of pre-existing events, nothing is showing. Also when selecting “Register event”, all the drop-down option sets with a large number of options are blank.
If I add ALL to the user role, or if I add all the individual authorisations, everything works fine.
Two questions:
Can anybody see which authorisation(s) is/are missing in the list above?
Where can I find an overview of all authorisations in the system with a detailed explanation of (a) what exactly that authorisation provides access to and (b) what authorisations have an impact on which areas (routine data capture/use, event data capture/use, tracker data capture/use).
As I said, we have tried adding EVERYTHING (every single permission) to the user role - it still does not work. The only way to make it work is by adding ALL (then it works even without any other permission set).
Checked the permissions you set. Not sure but can you try adding Add/Update Tracked Entity Instance. Strictly speaking an event does not have an entity but each record might be conceived as an instance. Worth trying I think. If it works then you want to also add Delete Tracked Entity Instance.
Let’s know if that helps.
Busoye
–
Busoye Anifalaje (PhD)
Director of Services (Principal), BAO Systems
UK: +44 7901-740-757 | US: +1 682-307-0986| busoye@baosystems.com | http://www.baosystems.com |
Skype: busoye | 2900 K Street, Suite 404, Washington D.C. 20007
YES, the program is added to the role, and its sharing is set to public view and edit (with login).
We have found earlier dev threads about very similar problems, but all indications are that those were fixed in 2.21. We have tested the latest 2.22 and the latest 2.23 - no difference. The only way to make it work is either to include ALL with that user role, or else log in as superuser. All other authorisations do not work.
Regards
Calle
On 6 July 2016 at 15:07, Busoye Anifalaje busoye@hisp.org wrote:
Hi Calle,
Have you added the event program to the role. The ALL authority is not a summation of all other permissions but a special designation that provides access to grant access to all apps and privately created objects (with the exception of dashboards).
Small correction: we have now ascertained that if the Data Capturer - Events have every single authorisation selected (except ALL), it does NOT work. If we on the other hand select ALL, then it works.
What is the difference between ALL and the sum of all individual authorisations?
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@hisp.org 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.
We have an instance with an Event program and a user role called “Data Capturer - Events” with the following authorisations - but one or more is missing:
Add/Update event
Add/Update Tracked Entity
Add/Update Tracked Entity Data Value
Delete Data Value
Generate Min-Max Value
Run validation
See Browser Cache Cleaner module
See Dashboard Intergration Module
See even Capture Module
See Event Report Module
See Event Visualiser module
See GIS Module
See Pivot table module
See report module
See validation rule
Something is missing, though - when a data capturer opens the Event Capture app and selects an orgunit with a number of pre-existing events, nothing is showing. Also when selecting “Register event”, all the drop-down option sets with a large number of options are blank.
If I add ALL to the user role, or if I add all the individual authorisations, everything works fine.
Two questions:
Can anybody see which authorisation(s) is/are missing in the list above?
Where can I find an overview of all authorisations in the system with a detailed explanation of (a) what exactly that authorisation provides access to and (b) what authorisations have an impact on which areas (routine data capture/use, event data capture/use, tracker data capture/use).
As I said, we have tried adding EVERYTHING (every single permission) to the user role - it still does not work. The only way to make it work is by adding ALL (then it works even without any other permission set).
Giving us grey hair, this problem is…
Regards
calle
Busoye Anifalaje (PhD)
Director of Services (Principal), BAO Systems
UK: +44 7901-740-757 | US: +1 682-307-0986| busoye@baosystems.com | http://www.baosystems.com |
Skype: busoye | 2900 K Street, Suite 404, Washington D.C. 20007
Checked the permissions you set. Not sure but can you try adding Add/Update Tracked Entity Instance. Strictly speaking an event does not have an entity but each record might be conceived as an instance. Worth trying I think. If it works then you want to also add Delete Tracked Entity Instance.
Busoye Anifalaje (PhD)
Director of Services (Principal), BAO Systems
UK: +44 7901-740-757 | US: +1 682-307-0986| busoye@baosystems.com | http://www.baosystems.com |
Skype: busoye | 2900 K Street, Suite 404, Washington D.C. 20007
YES, the program is added to the role, and its sharing is set to public view and edit (with login).
We have found earlier dev threads about very similar problems, but all indications are that those were fixed in 2.21. We have tested the latest 2.22 and the latest 2.23 - no difference. The only way to make it work is either to include ALL with that user role, or else log in as superuser. All other authorisations do not work.
Regards
Calle
On 6 July 2016 at 15:07, Busoye Anifalaje busoye@hisp.org wrote:
Hi Calle,
Have you added the event program to the role. The ALL authority is not a summation of all other permissions but a special designation that provides access to grant access to all apps and privately created objects (with the exception of dashboards).
Small correction: we have now ascertained that if the Data Capturer - Events have every single authorisation selected (except ALL), it does NOT work. If we on the other hand select ALL, then it works.
What is the difference between ALL and the sum of all individual authorisations?
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@hisp.org 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.
We have an instance with an Event program and a user role called “Data Capturer - Events” with the following authorisations - but one or more is missing:
Add/Update event
Add/Update Tracked Entity
Add/Update Tracked Entity Data Value
Delete Data Value
Generate Min-Max Value
Run validation
See Browser Cache Cleaner module
See Dashboard Intergration Module
See even Capture Module
See Event Report Module
See Event Visualiser module
See GIS Module
See Pivot table module
See report module
See validation rule
Something is missing, though - when a data capturer opens the Event Capture app and selects an orgunit with a number of pre-existing events, nothing is showing. Also when selecting “Register event”, all the drop-down option sets with a large number of options are blank.
If I add ALL to the user role, or if I add all the individual authorisations, everything works fine.
Two questions:
Can anybody see which authorisation(s) is/are missing in the list above?
Where can I find an overview of all authorisations in the system with a detailed explanation of (a) what exactly that authorisation provides access to and (b) what authorisations have an impact on which areas (routine data capture/use, event data capture/use, tracker data capture/use).
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@hisp.org 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.
···
From: Dhis2-devs [mailto:dhis2-devs-bounces+elmarie=hisp.org@lists.launchpad.net] On Behalf Of Adebusoye Anifalaje Sent: 06 July 2016 05:17 PM To: Calle Hedberg Cc: DHIS 2 developers Subject: Re: [Dhis2-devs] Data capturer - Events: Authorisation privilege missing
Got it Calle.
I just tested locally here and it works fine. Using
As I said, we have tried adding EVERYTHING (every single permission) to the user role - it still does not work. The only way to make it work is by adding ALL (then it works even without any other permission set).
Checked the permissions you set. Not sure but can you try adding Add/Update Tracked Entity Instance. Strictly speaking an event does not have an entity but each record might be conceived as an instance. Worth trying I think. If it works then you want to also add Delete Tracked Entity Instance.
YES, the program is added to the role, and its sharing is set to public view and edit (with login).
We have found earlier dev threads about very similar problems, but all indications are that those were fixed in 2.21. We have tested the latest 2.22 and the latest 2.23 - no difference. The only way to make it work is either to include ALL with that user role, or else log in as superuser. All other authorisations do not work.
Regards
Calle
On 6 July 2016 at 15:07, Busoye Anifalaje busoye@hisp.org wrote:
Hi Calle,
Have you added the event program to the role. The ALL authority is not a summation of all other permissions but a special designation that provides access to grant access to all apps and privately created objects (with the exception of dashboards).
Small correction: we have now ascertained that if the Data Capturer - Events have every single authorisation selected (except ALL), it does NOT work. If we on the other hand select ALL, then it works.
What is the difference between ALL and the sum of all individual authorisations?
We have an instance with an Event program and a user role called “Data Capturer - Events” with the following authorisations - but one or more is missing:
Add/Update event
Add/Update Tracked Entity
Add/Update Tracked Entity Data Value
Delete Data Value
Generate Min-Max Value
Run validation
See Browser Cache Cleaner module
See Dashboard Intergration Module
See even Capture Module
See Event Report Module
See Event Visualiser module
See GIS Module
See Pivot table module
See report module
See validation rule
Something is missing, though - when a data capturer opens the Event Capture app and selects an orgunit with a number of pre-existing events, nothing is showing. Also when selecting “Register event”, all the drop-down option sets with a large number of options are blank.
If I add ALL to the user role, or if I add all the individual authorisations, everything works fine.
Two questions:
Can anybody see which authorisation(s) is/are missing in the list above?
Where can I find an overview of all authorisations in the system with a detailed explanation of (a) what exactly that authorisation provides access to and (b) what authorisations have an impact on which areas (routine data capture/use, event data capture/use, tracker data capture/use).
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@hisp.org 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. 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@hisp.org 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 . 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@hisp.org 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.
From: Dhis2-devs [mailto:dhis2-devs-bounces+elmarie=hisp.org@lists.launchpad.net] On Behalf Of Adebusoye Anifalaje Sent: 06 July 2016 05:17 PM To: Calle Hedberg Cc: DHIS 2 developers Subject: Re: [Dhis2-devs] Data capturer - Events: Authorisation privilege missing
Got it Calle.
I just tested locally here and it works fine. Using
As I said, we have tried adding EVERYTHING (every single permission) to the user role - it still does not work. The only way to make it work is by adding ALL (then it works even without any other permission set).
Checked the permissions you set. Not sure but can you try adding Add/Update Tracked Entity Instance. Strictly speaking an event does not have an entity but each record might be conceived as an instance. Worth trying I think. If it works then you want to also add Delete Tracked Entity Instance.
YES, the program is added to the role, and its sharing is set to public view and edit (with login).
We have found earlier dev threads about very similar problems, but all indications are that those were fixed in 2.21. We have tested the latest 2.22 and the latest 2.23 - no difference. The only way to make it work is either to include ALL with that user role, or else log in as superuser. All other authorisations do not work.
Regards
Calle
On 6 July 2016 at 15:07, Busoye Anifalaje busoye@hisp.org wrote:
Hi Calle,
Have you added the event program to the role. The ALL authority is not a summation of all other permissions but a special designation that provides access to grant access to all apps and privately created objects (with the exception of dashboards).
Small correction: we have now ascertained that if the Data Capturer - Events have every single authorisation selected (except ALL), it does NOT work. If we on the other hand select ALL, then it works.
What is the difference between ALL and the sum of all individual authorisations?
We have an instance with an Event program and a user role called “Data Capturer - Events” with the following authorisations - but one or more is missing:
Add/Update event
Add/Update Tracked Entity
Add/Update Tracked Entity Data Value
Delete Data Value
Generate Min-Max Value
Run validation
See Browser Cache Cleaner module
See Dashboard Intergration Module
See even Capture Module
See Event Report Module
See Event Visualiser module
See GIS Module
See Pivot table module
See report module
See validation rule
Something is missing, though - when a data capturer opens the Event Capture app and selects an orgunit with a number of pre-existing events, nothing is showing. Also when selecting “Register event”, all the drop-down option sets with a large number of options are blank.
If I add ALL to the user role, or if I add all the individual authorisations, everything works fine.
Two questions:
Can anybody see which authorisation(s) is/are missing in the list above?
Where can I find an overview of all authorisations in the system with a detailed explanation of (a) what exactly that authorisation provides access to and (b) what authorisations have an impact on which areas (routine data capture/use, event data capture/use, tracker data capture/use).
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@hisp.org 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. 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@hisp.org 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.
Sounds like you have two unrelated problems, one is the list of events not showing. Edit the configuration of the program and check if "Display front page list” is set to No, change that to Yes.
Regarding sharing settings, I recommend that you check sharing for all the metadata involved in the program, starting with option sets.
About the user role, I see you are missing some of the delete authorities but that should not affect the ability to add new events and values.
I’m attaching an XML you can use to create a program with four data elements, one option set with 500 options, a user account and the user role that only allows access to the dashboard and event capture. That’s all you need to test a role with the basic authorities for data entry and a large option set, I tested it in 2.22 and the latest build of 2.24. In 2.22 if fails to link all the program stage data elements with the stage, it’s a bug I already discussed with Morten, so if you are going to test in that version I recommend importing without the program stage data elements and adding them manually.
Sorry I didn’t see your previous email indicating that you solved the matter and that it was indeed a sharing settings problem. Still, I hope you find the xml helpful to test a user role with the minimum authorities.
Checked the permissions you set. Not sure but can you try adding Add/Update Tracked Entity Instance. Strictly speaking an event does not have an entity but each record might be conceived as an instance. Worth trying I think. If it works then you want to also add Delete Tracked Entity Instance.
Let’s know if that helps.
Busoye
–
Busoye Anifalaje (PhD)
Director of Services (Principal), BAO Systems
UK: +44 7901-740-757 | US: +1 682-307-0986| busoye@baosystems.com | http://www.baosystems.com |
Skype: busoye | 2900 K Street, Suite 404, Washington D.C. 20007
YES, the program is added to the role, and its sharing is set to public view and edit (with login).
We have found earlier dev threads about very similar problems, but all indications are that those were fixed in 2.21. We have tested the latest 2.22 and the latest 2.23 - no difference. The only way to make it work is either to include ALL with that user role, or else log in as superuser. All other authorisations do not work.
Regards
Calle
On 6 July 2016 at 15:07, Busoye Anifalaje busoye@hisp.org wrote:
Hi Calle,
Have you added the event program to the role. The ALL authority is not a summation of all other permissions but a special designation that provides access to grant access to all apps and privately created objects (with the exception of dashboards).
Small correction: we have now ascertained that if the Data Capturer - Events have every single authorisation selected (except ALL), it does NOT work. If we on the other hand select ALL, then it works.
What is the difference between ALL and the sum of all individual authorisations?
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@hisp.org 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.
We have an instance with an Event program and a user role called “Data Capturer - Events” with the following authorisations - but one or more is missing:
Add/Update event
Add/Update Tracked Entity
Add/Update Tracked Entity Data Value
Delete Data Value
Generate Min-Max Value
Run validation
See Browser Cache Cleaner module
See Dashboard Intergration Module
See even Capture Module
See Event Report Module
See Event Visualiser module
See GIS Module
See Pivot table module
See report module
See validation rule
Something is missing, though - when a data capturer opens the Event Capture app and selects an orgunit with a number of pre-existing events, nothing is showing. Also when selecting “Register event”, all the drop-down option sets with a large number of options are blank.
If I add ALL to the user role, or if I add all the individual authorisations, everything works fine.
Two questions:
Can anybody see which authorisation(s) is/are missing in the list above?
Where can I find an overview of all authorisations in the system with a detailed explanation of (a) what exactly that authorisation provides access to and (b) what authorisations have an impact on which areas (routine data capture/use, event data capture/use, tracker data capture/use).