LMS Access by Role
My Role
User Experience / Product Designer
Deliverables
Figma mockup, FigJam flows
Tools
Figma
Use case
How different roles access either to edit or just view information regarding student into the LMS so that a new role “Observer” could be implemented properly.
Challenges
Identify main user scenarios and user needs.
Requirements, scope, and feasibility.
likely edge cases and access conflicts with other role within the platform.
The Observer role is given to users that need view only access to course.
Understanding the problem
In order to understand the complexity of the new role access, I conducted a user flow analysis to map who would manage the role, who could grant permissions on that role, and how that role would access the LMS.
Besides, I mapped all potential user scenarios and access points for each role, which allowed me to validate specific needs, technical requirements and likely usability issues.
Exploring and creating
In addition, and based on the initial flow, sketching helped me outline what the UI would look like and understand each touch point on it.
I then presented the proposal as a prototype to a user focus group to get feedback on it, while validating the technical feasibility with the development team to define milestones and likely delivery dates.
Takeaways
Integrating the "Observer" role into the LMS demanded a comprehensive analysis of user scenarios, access points and potential conflicts. By meticulously mapping user flows and validating technical requirements through prototyping and user feedback, we guaranteed a seamless implementation that met user needs and maintained system integrity. This process is a clear example of why thorough planning and collaboration are crucial for successful feature integration.