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
The structure in C2 allows us to assign several roles to the same user. However, the interface to do that is still missing.
Change the dropdown box in the user edition page to allow for a multiple-select. Make it 8 rows high to make sure we see most of the roles in one single step.
Update the users list (as admin) to show the multiple roles of each user (one role per line).
Make sure the advanced search works with multiple roles (that it can find users of any role or any combination of roles).
Adapt the api_is_allowed_to_edit() function to use the method developed in #5644. The permissions should be the final result of checking for permissions by all available roles on the item we're looking at. Whenever the edition is just about an item in the course where the teacher is assigned, make sure you bypass all this. Permissions are only important for (few) specific items inside courses and most items outside the courses (skills, badges, sessions, users, settings, etc).
Maybe have a static list of things to check for inside the api_is_allowed_to_edit() function and check it quickly before going deeper to api_get_permission()?
The text was updated successfully, but these errors were encountered:
The structure in C2 allows us to assign several roles to the same user. However, the interface to do that is still missing.
Change the dropdown box in the user edition page to allow for a multiple-select. Make it 8 rows high to make sure we see most of the roles in one single step.
Update the users list (as admin) to show the multiple roles of each user (one role per line).
Make sure the advanced search works with multiple roles (that it can find users of any role or any combination of roles).
Adapt the api_is_allowed_to_edit() function to use the method developed in #5644. The permissions should be the final result of checking for permissions by all available roles on the item we're looking at. Whenever the edition is just about an item in the course where the teacher is assigned, make sure you bypass all this. Permissions are only important for (few) specific items inside courses and most items outside the courses (skills, badges, sessions, users, settings, etc).
Maybe have a static list of things to check for inside the api_is_allowed_to_edit() function and check it quickly before going deeper to api_get_permission()?
The text was updated successfully, but these errors were encountered: