-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Workflows #165
Comments
@LeScruf Do we want to moderate all types of content? The content that is created manually is:
Do data entrants, field officers and field managers enter all of these, or are there some that don't need to be moderated because they are entered by an LMO? |
|
Hi @Rashids2021 @LeScruf . Can you confirm the following roles/permissions please? Data entrants are users with one of these roles:
When power users create or edit Offer/license and Sub areas they are subject to moderation. Changes must be approved by the LMO. We will create an LMO (Land management officer) role with permission to approve and publish the moderated offer licenses and subareas All other roles, including NFA Staff, Non-staff will have read-only permission on all content types. Questions |
LMO (Land management officer) > HQ moderator We should moderate the farmer details content type. |
A straight-forward (we hope!) work flow for the tree farmer system which applies to all data entered. This is bad design because the Land Management Officer stands to become a major bottleneck in the publishing of data to the system.
One solution to this design issue is simply to be able to assign other selected users equivalent permissions to approve / reject the data entered and submitted for approval (the easiest option).
Another option is have all data fields being marked as either needing to be approved or not needing to be approved (and perhaps this is something that can be exposed as an administrator table - so that this binary option can be adjusted for each data field). Or alternatively (and less desirably in terms of flexibility) is for the workflow to be hard coded to select specific data fields and not others.
The text was updated successfully, but these errors were encountered: