feat: remove legacy library user access, import, and export pages

[salman2013]

Summary

This PR removes three legacy v1 content library UI pages from Studio (CMS) and cleans up all associated dead code.

Changes

1. Remove the legacy library user access page

• Deleted manage_library_users view from library.py
• Removed URL pattern /library/<key>/team/ from cms/urls.py
• Deleted template manage_users_lib.html
• Deleted JS factory manage_users_lib.js
• Deleted JS spec library_users_spec.js and mock templates
• Removed User Access nav links from header.html

2. Remove the legacy library import page

• Removed library branch from import_handler in import_export.py
• Removed library-specific content from import.html
• Removed library branch from import.js factory

3. Remove the legacy library export page

• Removed library branch from export_handler in import_export.py
• Removed library-specific content from export.html
• Removed isLibrary and library branches from export.js and factories/export.js

4. Search and destroy unused REST APIs and utility code

• Removed library-specific role hierarchy (LibraryUserRole) from _course_team_user REST API in user.py
• Removed is_library check and not is_library auto-enrollment guard from user.py
• Removed unused imports: LibraryLocator, LibraryUserRole from user.py; render_to_response, reverse_library_url from import_export.py

Test plan

• Verify course import and export pages still work correctly
• Verify course team management still works correctly

[openedx-webhooks]

Thanks for the pull request, @salman2013!

This repository is currently maintained by @openedx/wg-maintenance-openedx-platform.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[Copilot]

Pull request overview

Removes legacy Studio (CMS) UI surfaces specific to legacy (v1) content libraries, including library user-access management and library import/export pages, and simplifies import/export codepaths to be course-only.

Changes:

• Removed the legacy “Library User Access” route/view/template and its JS factory/spec mocks.
• Removed library-specific navigation items (User Access / Import / Export) from the library header UI.
• Simplified import/export templates and JS factories/views to remove library branching and parameters.

Reviewed changes

Copilot reviewed 16 out of 16 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
cms/urls.py	Removes the manage_library_users URL route for libraries.
cms/templates/widgets/header.html	Removes library header dropdown links for User Access / Import / Export.
cms/templates/manage_users_lib.html	Deletes the legacy library user-access management page template.
cms/templates/js/mock/mock-manage-users-lib.underscore	Deletes mock fixture for library user-access page (RW).
cms/templates/js/mock/mock-manage-users-lib-ro.underscore	Deletes mock fixture for library user-access page (RO).
cms/templates/import.html	Removes library-specific import copy/logic; makes template course-only.
cms/templates/export.html	Removes library-specific export copy/logic; makes template course-only.
cms/static/js/views/export.js	Removes isLibrary state and library-specific error messaging paths.
cms/static/js/spec/views/pages/library_users_spec.js	Deletes Jasmine spec for legacy library user-access page.
cms/static/js/features/import/factories/import.js	Removes library parameter handling; now course-only import messaging.
cms/static/js/factories/manage_users_lib.js	Deletes legacy JS factory for library user-access page.
cms/static/js/factories/export.js	Updates factory signature and calls to match course-only export behavior.
cms/static/cms/js/spec/main.js	Removes deleted library_users_spec from the spec bundle.
cms/djangoapps/contentstore/views/tests/test_library.py	Removes test coverage tied specifically to the deleted legacy user-access page.
cms/djangoapps/contentstore/views/library.py	Removes manage_library_users view and related imports/exports.
cms/djangoapps/contentstore/views/import_export.py	Removes legacy library export rendering; redirects export HTML to MFE; import HTML redirect remains.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[irfanuddinahmad]

reverse_library_url is still imported here but its only caller — manage_library_users — was deleted in this PR. This will produce a linter warning. Safe to remove from the import line.

[salman2013]

reverse_library_url is still in use at library.py:267 for the library_handler URL, so it can't be removed.

[irfanuddinahmad]

No test coverage for library key behavior in import_handler / export_handler

The test plan checks that course import/export pages still work, but there are no tests asserting what happens when either handler receives a LibraryLocator key now that the library branches have been removed:

• import_handler (GET): now always calls redirect(get_import_url(courselike_key)) — for a library key this redirects to /course/library-v1:.../import which is invalid in the MFE.
• export_handler (GET): now calls modulestore().get_course(course_key) then raises Http404 if None — a library key will always return None here, so it 404s silently.

These two paths now diverge (one redirects incorrectly, one 404s), and neither outcome is tested. Even a simple test asserting the expected status code/redirect for each handler when passed a library key would prevent regressions if the behavior needs to change later.