You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, Admins and Super Admins have full edit/delete ability for all queries. We should consider whether we want this to be the case, or whether we should limit that functionality to the query's author.
Ex. Admin A creates an Influenza query, and assigns it to the Influenza user group. Admin B is a member of the Influenza user group. Super Admin C is not a member.
Should Admin B be able to edit/delete the query, because they are a member of the assigned group? Should they be able to edit/delete queries for groups they are not assigned to?
Should Super Admin C be able to edit/delete the query, even though they aren't in the group, because they are a Super Admin?
Should edit/delete be restricted to only the query's author? Or the query's author and Super Admins?
Should any Admin or Super Admin be able to edit/delete any query? (Leave current behavior as-is)
etc.
Acceptance Criteria:
The team has agreed on what level of permissions to support for editing/deleting queries
(if needed) Code and documentation is updated to reflect those permission changes
The text was updated successfully, but these errors were encountered:
Description:
Currently, Admins and Super Admins have full edit/delete ability for all queries. We should consider whether we want this to be the case, or whether we should limit that functionality to the query's author.
Ex. Admin A creates an Influenza query, and assigns it to the Influenza user group. Admin B is a member of the Influenza user group. Super Admin C is not a member.
Acceptance Criteria:
The text was updated successfully, but these errors were encountered: