docs: apply feedback

Author: MaferMazu

oeps/best-practices/oep-0066-bp-authorization.rst

@@ -11,9 +11,9 @@ OEP-66: User Authorization
    * - Title
      - User Authorization
    * - Last Modified
-     - 2023-10-20
+     - 2025-12-15
    * - Authors
-     - Hilary Sinkoff (hsinkoff@2u.com), Jeremy Bowman (jbowman@edx.org)
+     - Hilary Sinkoff (hsinkoff@2u.com), Jeremy Bowman (jbowman@edx.org), Maria F Magallanes (maria.magallanes@edunext.co)
    * - Arbiter
      - Feanil Patel (feanil@axim.org)
    * - Status
@@ -479,6 +479,8 @@ authn data point, but is an accepted way to implement feature specific roles and
 It is advisable to be very careful regarding the jwt token header limits if adding a new feature specific
 set of roles using this implementation path.
 
+.. _openedx-authz-section:
+
 openedx-authz
 -------------
 
@@ -498,13 +500,12 @@ For more information, see the `openedx-authz documentation`_ and the `openedx-au
 content libraries
 ------------------
 
-Permission is granted on a Feature, in this case Content Library.
+Roles and permissions are granted on a per-library basis for v2 content libraries.
 
-Permission is assigned in the CMS exclusively for providing explicit permission to
-view or edit a library in the CMS.
+Explicit roles can be assigned through Studio by accessing the library and selecting the "Manage Team" option. This provides granular control over who can view, edit, or administer each content library.
 
-It grants access on a library by library basis and is used for v2 of content libraries
-in the CMS.
+.. note::
+  Since Ulmo, these permissions are handled by :ref:`openedx-authz <openedx-authz-section>`.
 
 .. note::
   v1 libraries (deprecated) granted access to libraries on a course by course basis