Features that will be implemented to enhance FOLIO's ability to support consortia (Phase 1) (UXPROD-4049)

[UXPROD-4055] CRUD affiliations and related permissions of a given user Created: 09/Feb/23  Updated: 30/Nov/23  Resolved: 04/Oct/23

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Poppy (R2 2023)
Parent: Features that will be implemented to enhance FOLIO's ability to support consortia (Phase 1)

Type: New Feature Priority: P1
Reporter: Dennis Bridges Assignee: Dennis Bridges
Resolution: Done Votes: 0
Labels: LC1, ecs, loc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
clones UXPROD-4044 Context switching for staff user with... Closed
Defines
is defined by FOLIO-3755 Setup Thunderjet rancher environment ... Closed
is defined by UIU-2800 View affiliation associated permissions Closed
is defined by UIU-2801 Assign/unassign a users affiliations Closed
is defined by UIU-2805 Add/Edit a users permissions for asso... Closed
is defined by UIU-2821 View a users affiliations accordion i... Closed
is defined by UIU-2852 Success and Error toasts - Assign/una... Closed
is defined by MODCON-31 Change unique index to use userId and... Closed
is defined by MODCON-33 Delete shadow users when real user wa... Closed
is defined by MODCON-40 Populate admin user with predefined p... Closed
is defined by FAT-6028 Cover Consortia User Tenant associati... Closed
is defined by MODCON-3 Define DB schema for storing user and... Closed
is defined by MODCON-9 Implement endpoint to retrieve list o... Closed
is defined by MODCON-10 Implement endpoint to add user affili... Closed
is defined by MODCON-11 Process kafka event from mod-users to... Closed
is defined by MODCON-12 Implement endpoint to remove user ass... Closed
is defined by MODCON-14 Process kafka event from mod-users to... Closed
is defined by MODCON-16 Spike: Investigate an approach how to... Closed
is defined by MODCON-25 Create Primary Affiliations When Add... Closed
is defined by MODCON-30 Exception handling for Assign/unassig... Closed
is defined by MODCON-32 Store central tenant id for each inst... Closed
is defined by MODCON-36 Populate default user permissions whe... Closed
is defined by MODCON-43 Create system user to support all act... Closed
is defined by MODUSERS-347 Implement sending USER_CREATED event ... Closed
is defined by MODUSERS-350 Implement sending USER_DELETED event ... Closed
Release: Poppy (R2 2023)
Epic Link: Features that will be implemented to enhance FOLIO's ability to support consortia (Phase 1)
Front End Estimate: Large < 10 days
Front-End Confidence factor: 50%
Back End Estimate: Small < 3 days
Back-End Confidence factor: 50%
Development Team: Thunderjet
PO Rank: 0
Rank: Cornell (Full Sum 2021): R5

 Description   

Current situation or problem: Users are not able to have multiple affiliations with unique permissions for different libraries in a consortia

In scope

Allow user with the appropriate permissions to view user records and identify their affiliation(s)

Allow user with the appropriate permissions to Add/edit the affiliation(s) and associated permissions of a given user record

Display all permissions for each affiliation the user has

Out of scope

Update permissions for more that one affiliation with a single action

Update permissions for a single affiliation for more than one user with a single action

Use case(s)

see linked document for more details

Links to additional info

see linked document for more details

Questions



 Comments   
Comment by Erin Nettifee [ 16/Feb/23 ]

If a library is not in a FOLIO-based consortia, they won't want to have the UX change - but the idea of seeing permissions assigned to a user is appealing. Is there a way to enable the permissions assigned to a user for libraries without adding extra stuff to the UX that they don't want? Has the Users SIG had a chance to talk about any of this yet?

Comment by Dennis Bridges [ 04/Oct/23 ]

All related stories completed for code freeze

Generated at Fri Feb 09 00:36:54 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.