-
Notifications
You must be signed in to change notification settings - Fork 5
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
E12 team to provide custom permissions table #544
Comments
These map roles to groups.
Basic permissions are already mapped to groups and agreed CAN_LOCK_CHILD_CASE_DATA_FROM_EDITING
CAN_UNLOCK_CHILD_CASE_DATA_FROM_EDITING
CAN_OPT_OUT_CHILD_FROM_INCLUSION_IN_AUDIT
CAN_APPROVE_ELIGIBILITY
CAN_REGISTER_CHILD_IN_EPILEPSY12
CAN_UNREGISTER_CHILD_IN_EPILEPSY12
CAN_EDIT_EPILEPSY12_LEAD_CENTRE
CAN_ALLOCATE_EPILEPSY12_LEAD_CENTRE
CAN_TRANSFER_EPILEPSY12_LEAD_CENTRE
CAN_DELETE_EPILEPSY12_LEAD_CENTRE
CAN_CONSENT_TO_AUDIT_PARTICIPATION @AmaniKrayemRCPCH @nikyraja could you please allocate permissions to groups? |
to confirm, by 'Register' you mean to add a new patient? If so, the below is correct.
|
sorry, slight edit to the trust_audit_team_view_only permissions
|
Thank you
By register, I mean complete the registration. That is not the same as creating a case – it involves agreeing eligibility, setting the FPA date and confirming the lead centre. It maybe this permission is not needed but currently it exists and is allocated as listed
S
From: Amani Krayem ***@***.***>
Date: Thursday, 24 August 2023 at 09:26
To: rcpch/rcpch-audit-engine ***@***.***>
Cc: Simon Chapman ***@***.***>, Comment ***@***.***>
Subject: Re: [rcpch/rcpch-audit-engine] E12 team to provide custom permissions table (Issue #544)
sorry, slight edit to the trust_audit_team_view_only permissions
Group
Permissions
trust_audit_team_view_only
CAN_LOCK_CHILD_CASE_DATA_FROM_EDITINGCAN_UNLOCK_CHILD_CASE_DATA_FROM_EDITINGCAN_OPT_OUT_CHILD_FROM_INCLUSION_IN_THE_AUDITCAN_REGISTER_CHILD_IN_EPILEPSY12
trust_audit_team_edit_access
CAN_LOCK_CHILD_CASE_DATA_FROM_EDITINGCAN_UNLOCK_CHILD_CASE_DATA_FROM_EDITINGCAN_OPT_OUT_CHILD_FROM_INCLUSION_IN_THE_AUDITCAN_APPROVE_ELIGIBILITYCAN_REGISTER_CHILD_IN_EPILEPSY12CAN_ALLOCATE_EPILEPSY12_LEAD_CENTRE
trust_audit_team_full_access
CAN_LOCK_CHILD_CASE_DATA_FROM_EDITINGCAN_UNLOCK_CHILD_CASE_DATA_FROM_EDITINGCAN_OPT_OUT_CHILD_FROM_INCLUSION_IN_THE_AUDITCAN_APPROVE_ELIGIBILITYCAN_REGISTER_CHILD_IN_EPILEPSY12CAN_UNREGISTER_CHILD_IN_EPILEPSY12CAN_EDIT_EPILEPSY12_LEAD_CENTRECAN_ALLOCATE_EPILEPSY12_LEAD_CENTRECAN_TRASNFER_EPILEPSY12_LEAD_CENTRECAN_DELETE_EPILEPSY12_LEAD_CENTRE
epilepsy12_audit_team_full_access
CAN_LOCK_CHILD_CASE_DATA_FROM_EDITINGCAN_UNLOCK_CHILD_CASE_DATA_FROM_EDITINGCAN_OPT_OUT_CHILD_FROM_INCLUSION_IN_THE_AUDITCAN_APPROVE_ELIGIBILITYCAN_REGISTER_CHILD_IN_EPILEPSY12CAN_UNREGISTER_CHILD_IN_EPILEPSY12CAN_EDIT_EPILEPSY12_LEAD_CENTRECAN_ALLOCATE_EPILEPSY12_LEAD_CENTRECAN_TRASNFER_EPILEPSY12_LEAD_CENTRECAN_DELETE_EPILEPSY12_LEAD_CENTRE
patient_access
CAN_CONSENT_TO_AUDIT_PARTICIPATION
—
Reply to this email directly, view it on GitHub<#544 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAICOV52BZ3MIVOIBJDIEE3XW4F2PANCNFSM6AAAAAA3EL4WGQ>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Ah understood. Ok, the correct version of the permissions table is below
|
Can I check on the status of this? Has it been actioned? Is this related to #541 |
This still needs implementing |
tidy permissions as per e12 issue #544
closed with #640 |
Update docs perms table once provided
The text was updated successfully, but these errors were encountered: