Migrate Open edX Course Roles to Verawood RBAC
Migrate one Open edX Verawood course from legacy Studio roles to openedx-authz, enable course-scoped RBAC, then verify Course Admin, Course Staff, learner, enrollment, and Django Admin boundaries.
What you will accomplish
One Open edX course migrated to Verawood's course-authoring RBAC model, with course-scoped roles and permission boundaries verified.
Environment covered
Open edX Verawood · Tutor 22 · openedx-authz · course-scoped RBAC
The exact commands for this tutorial are maintained as a GitHub Gist, which stays the canonical command reference.
What the demonstration proves: one existing course was migrated from legacy CourseAccessRole records to openedx-authz with authz.enable_course_authoring enabled for that course; Course Admin manages the course team, Course Staff edits and publishes without managing roles, the learner consumes the published course without Studio access, course-authoring roles stay separate from LMS enrollment, and neither course-scoped role gains global LMS or Studio Django Admin access. That is a controlled migration and permission test for one course in the declared Verawood and Tutor environment. It does not demonstrate an organization-wide or platform-wide RBAC rollout, enterprise identity and access management, every available Open edX role, global administration, bulk account provisioning, manual rollback execution, high availability, or production-scale authorization governance.
This is practical lab and tutorial guidance. A working lab, a public demonstration system, and a production environment are not the same thing: check capacity, data protection, change control, and recovery requirements before applying any of it to a system that people depend on.