Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Restrict multiple access to read-only user type across the platform #5424

Closed
8 tasks done
nihal467 opened this issue May 2, 2023 · 2 comments · Fixed by #5425
Closed
8 tasks done

Restrict multiple access to read-only user type across the platform #5424

nihal467 opened this issue May 2, 2023 · 2 comments · Fixed by #5425
Assignees
@rithviknishad
Labels
P1 breaking issue or vital feature urgent

Comments

@nihal467
Copy link
Member

nihal467 commented May 2, 2023 •
edited by rithviknishad
Loading

Describe the bug

Read-only users (staff read-only, District admin read-only, State admin read-only) are having the following access which they shouldn't be having it

  • We are able to edit and configuration of an already existing asset
  • We are able to create new assets by using the "Create asset" button in the asset tab
  • We are able to upload files to a patient consultation page
  • We are able to create an investigation on a patient consultation page

Expected behavior
image

  • Create asset button should be disabled on the asset page for all read-only users.

image

  • update and configure button should be disabled on the asset details page for all read-only users.

image

  • record and choose file button should be disabled on the patient consultation page for all read-only user.

image

  • log lab result button should be disabled on the patient consultation page for all read-only user.
@nihal467 nihal467 added urgent P1 breaking issue or vital feature labels May 2, 2023
@github-actions
Copy link

github-actions bot commented May 2, 2023

⚠️ Refrain from assigning this issue to yourself if you have another P1 issue assigned that is not yet closed.

@nihal467 nihal467 added P1 breaking issue or vital feature and removed P1 breaking issue or vital feature labels May 2, 2023
@github-actions
Copy link

github-actions bot commented May 2, 2023

⚠️ Refrain from assigning this issue to yourself if you have another P1 issue assigned that is not yet closed.

@rithviknishad rithviknishad self-assigned this May 2, 2023
rithviknishad added a commit that referenced this issue May 2, 2023
@rithviknishad
fixes #5424
e393f6e
@rithviknishad rithviknishad mentioned this issue May 2, 2023
Merged
6 tasks
khavinshankar pushed a commit that referenced this issue May 2, 2023
@rithviknishad @nihal467
Disables multiple buttons for read only users (#5425)
29e08db 
* fixes #5424

* fix `ButtonV2`'s Authorized wrapper not returned

* disable for Asset Delete Button

---------

Co-authored-by: Mohammed Nihal <57055998+nihal467@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rithviknishad rithviknishad

Labels
P1 breaking issue or vital feature urgent
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Disables multiple buttons for read only users coronasafe/care_fe
2 participants
@rithviknishad @nihal467