-
Notifications
You must be signed in to change notification settings - Fork 1
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
Improvements to the Limited Staff role experience #361
Comments
Thanks for your submission, @openedx/open-edx-project-managers will review shortly. |
@arbrandes @brian-smith-tcril Could you please add any technical requirements you'd like to see here? |
In order to be able to fully test the Limited Staff role UX, I'd want to know:
Answers to the previous questions would help inform my thoughts on this from a technical implementation perspective:
|
Limited Staff should not have access to any of the Studio pages in the course-authoring MFE. @0x29a as the contributing author for this role, is there anything you'd add here? openedx/edx-platform#32570 |
No, @jmakowski1123, this description is correct. cc @Agrendalath |
@jmakowski1123 It looks like the following PRs are providing a partial implementation of this proposal:
Could you please have a look at those and let us know what the next steps are from the product perspective? |
@jmakowski1123 Could you please have a look at the comment above and let us know how to proceed? (Happy to ping someone else from the product working group if you'd prefer. Let me know.) |
The Limited Staff role needs some improvements to the user experience.
Currently, when a user with the Limited Staff role lands on a Studio Page in the new course-authoring MFE, they are blocked by a 403 error message, which contains json fields and is difficult to interpret. Minimally, the messaging could be improved to explain that the user is not granted access to Studio.
An enhancement can be made in the Studio experience such that users with this role do not see the "View this course in Studio" button. This will greatly reduce the chance of users trying to access parts of the platform that they don't have access to.
The text was updated successfully, but these errors were encountered: