-
Notifications
You must be signed in to change notification settings - Fork 475
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
Refactoring the access of a district admin in respect to list of users #7500
Comments
Actually I as well encountered the issue, but am not sure whether this is an actual issue or some role-based feature. |
@kabirrajsingh if your PR solves multiple issues, then I guess you should go ahead with my issue as well... But first get the conformation . |
@Sulochan-khadka it is actually a restriction on the basis of District, I raised the issue in the last standup. A district admin can only use the action buttons in his own district, which in this case is Thiruvananthapuram. When you try to use it on user from another district like Ernakulam, it would throw an error. We can work on this together but the issue needs discussion first as to which approach would be the best to solve it. |
@kabirrajsingh Yeah I guess this issue will be addressed once it comes to the attention of the contributors. |
Hi, @gigincg, @nihal467, @khavinshankar, @mathew-alex, @aparnacoronasafe, This issue has been automatically marked as stale because it has not had any recent activity. |
the issue has been already handled in the ohcnetwork/care#1742 |
#needs-discussion
Currently a district admin has access to view all the users from the users tab.
But he/she cannot perform any function on it if the user is not from his own district, basically cannot utilize the Linked facility, Linked Skills and set weekly average hours button. When he tries to perform such an operation, it gives an error from the backend but this issue could be handled better.
Suggested changes-
Solving this issue would also solve #7497 .
This could also be extended to solve #7374
@coronasafe/code-reviewers
The text was updated successfully, but these errors were encountered: