Design: Course Editor & Course Auditor screen restrictions

[MaferMazu]

Overview

Review the current permissions table to identify specific limitations for the Course Editor and Course Auditor roles. The goal is to define how the UI should handle restricted actions and unauthorized views for these users.

Scope of Work

• Audit Permissions: Map out all actions and views that are restricted for both roles based on the permissions matrix.
• UX Gap Analysis: Identify where these restrictions currently cause friction or "dead ends" in the interface.
• Proposal: Create a proposal with UI solutions for "no-access" states (e.g., disabled buttons, tooltips, or hidden sections).

Reference

• https://apps.verawood.demo.edly.io/admin-console/authz

[MaferMazu]

cc @maguilarUXUI

[MaferMazu]

@maguilarUXUI, I don't know if you have it on your radar, but we've already started implementing part of this.

More details: #284

[maguilarUXUI]

https://www.figma.com/design/onU2END2OXaF7RRLWEHsZI/AuthZ---v2?node-id=9148-6010&t=pIC705UCzs27xOyV-0 @bra-i-am

[MaferMazu]

@maguilarUXUI thanks a lot for the proposal ✨

@bra-i-am the link that @maguilarUXUI shared is the proposal for the views related to the course editor and auditor based on their read-only permissions.

This card blocks #284. Can you help me review the designs so we can refine the #284?