Details
-
New Feature
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
Description
The following "logical" permissions (some of them need to be modelled as "sets") should be captured in the MDs for mod-users and mod-auth:
Let's discuss if there are any issues with this.
TestRail: Results
Attachments
Issue Links
- blocks
-
FOLIO-552 Test Site Issues
-
- Closed
-
-
LIBAPP-146 Permissions: Can Create New User
-
- Closed
-
-
LIBAPP-151 Permissions: Can Create, Edit and Remove Permission Sets
-
- Closed
-
-
STRIPES-270 Permissions: Getting Fetch Errors When Logging In With Create User Permission
-
- Closed
-
-
STRIPES-304 Update the permissions that the Users app checks
-
- Closed
-
-
STRIPES-326 Update all client-side permission names to match new backend
-
- Closed
-
- is blocked by
-
DMOD-212 create ModuleDescriptors for auth and users modules
-
- Closed
-
-
FOLIO-526 Guidelines for module permissions
-
- Closed
-
-
FOLIO-540 update bb with modules (mod-auth, mod-users) that support permission loading
-
- Closed
-
-
OKAPI-267 Define permission sets in ModuleDescriptor
-
- Closed
-
- relates to
-
DMOD-178 mod-perms: implement permission loading interface
-
- Closed
-
-
CIRC-1 Adapt circulation module to use new Okapi path filtering
-
- Closed
-
-
CIRCSTORE-3 Adapt loan storage module to use new Okapi path filtering
-
- Closed
-
-
DMOD-201 ensure we can filter on the criteria needed by the CRUD permission screen
-
- Closed
-
-
STRIPES-269 Permissions: Only Defined Permissions Should Display in the Permissions Menu
-
- Closed
-