Skip to content

[DEPR]: Libraries' Roles and Permission System #37409

Open

Description

@MaferMazu

RFC Start Date

2025-10-16

Target Plan Accepted Date

2025-10-30

Target Transition Unblocked Date

December 2025 (With Ulmo cut)

Earliest Breaking Changes Unblocked Date

April 2026

Earliest Open edX Named Release with Breaking Changes

Willow

Rationale

The Roles and Permissions improvement project aims to enhance the management of permissions on the Open edX platform. To mitigate the possible risk associated with completely overhauling a core system like authorization, our primary strategy is to implement a staging or phased migration plan. We will start migrating the current library permissions and roles to the new authorization system.

Removal

Replacement

Deprecation

  • We'll mark the rest api methods regarding authorization in content libraries as depr.
  • We'll mark the ContentLibraryPermission model as depr.

#38052

Additional Info

Note

For the Ulmo release, we are going to add this new authorization system without removing the existing one, following the expand-contract deprecation model.

More information: openedx/openedx-authz#66

Task List (Transition Unblocked)

  • Having a migration script to transform existing explicit role assignments into the new authorization model

Task List (DEPR)

  • Remove the code mentioned in the removal section. - planned for Willow.

Activity

  1. added
    deprProposal for deprecation & removal per OEP-21
    on Oct 1, 2025
  2. feanil commented on Jan 8, 2026

    @feanil
    Contributor

    @MaferMazu are there any operator changes here, is there an operator scrip that operators need to run or will it be automatic?

    This DEPR may not be needed if there is no end-user or operator impact so we're looking to better understand what the plan is before the next named release.

  3. MaferMazu commented on Jan 8, 2026

    @MaferMazu
    ContributorAuthor

    @MaferMazu are there any operator changes here, is there an operator scrip that operators need to run or will it be automatic?

    No, there is no operator change here.

    We migrate the content library data via a Django migration, which is performed automatically. Details: openedx/openedx-authz#134


    The only possible impact we had for operators or end-users is the changes in Django Admin, if someone sets the library team in the content library module in Django Admin, it won't have an effect. - It is a hidden way, but it is a way. And I forgot to mark it as deprecated or directly remove the inline of the admin page before the Ulmo release.

    I can open a PR about it, but I'm not sure we still need this DEPR ticket. What do you think?

    Image Django Admin Page affected.
  4. feanil commented on Jan 14, 2026

    @feanil
    Contributor

    Gotcha, is it possible to just remove the option to change the library teams via django admin if it's going to have no effect? Then people can't do the wrong things and expect them to work. It sounds like this DEPR is useful for maybe communicating that the admin UI for managing library permissions is going away?

  5. moved this from RFC to Plan Accepted in DEPR: Deprecation & Removalon Jan 22, 2026
  6. dianakhuang commented on Jan 22, 2026

    @dianakhuang
    Contributor

    We think that this is worth a DEPR, even if we think the DEPR impact will be low. We don't need a long comment period for this, so we can move it into Plan Accepted.

  7. moved this from Plan Accepted to Breaking Changes Unblocked in DEPR: Deprecation & Removalon Jan 22, 2026
  8. added theissue type on Jan 28, 2026
  9. BryanttV commented on Feb 26, 2026

    @BryanttV
    Contributor

    Hello! I created a PR to mark the Libraries v2 roles and permissions code as deprecated: #38052. I’d appreciate it if you could take a look and share your feedback. Thanks in advance!

    cc @feanil @dianakhuang

  10. mariajgrimaldi commented on Apr 27, 2026

    @mariajgrimaldi
    Member

    @BryanttV can we update the target removal date for Willow? Since it is already marked as deprecated, an extra release window makes sense

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    deprProposal for deprecation & removal per OEP-21

    Type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions