Loans (UXPROD-788)

[UXPROD-3158] Users App and Loans - New/Expanded Permissions Created: 01/Jul/21  Updated: 13/Jun/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Loans

Type: New Feature Priority: TBD
Reporter: Erin Nettifee Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: enettifee-reviewed
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
clones UXPROD-3157 Check in - add permission control for... Draft
Defines
is defined by UIU-1624 Permissions: export overdue loans Open
is defined by UIU-624 Permissions for change due date (adva... Open
is defined by UIU-1625 Permissions: export user's open or cl... Open
is defined by UIU-622 Permissions for viewing open loans in... Draft
is defined by UIU-623 Permissions for viewing closed loans Draft
Relates
relates to UXPROD-1985 Loans: Permissions (Action-based) Closed
relates to UXPROD-3159 User Permission Management UI Improve... Open
Epic Link: Loans
Development Team: Vega
PO Rank: 0
Rank: Cornell (Full Sum 2021): R3
Rank: Mainz (Full TBD): R3
Rank: MTSU: R4
Rank: MO State (MVP June 2020): R4

 Description   

Current situation or problem

FOLIO provides some permissions (view loans, renew loans, change due date, check out, overrides, etc.) based on existing endpoints. There are, however, needed permissions for viewing loans in the Users app that do not have associated endpoints:

  • Permissions to view only open loans;
  • Permissions to view only closed loans;
  • Permissions for changing a due date;
  • Permissions to export open, closed, or overdue loans;

Early on, there was a project decision that we needed to define a project-wide approach to action based permissions. However, that did not happen, and a further decision was made that individual features should be prioritized and proceed based on their app's individual needs. See the conversation on https://folio-org.atlassian.net/browse/UXPROD-1828

In scope

Out of scope

Use case(s)

  • A library may decide not to anonymize closed loans (esp. if needed customization is still in development,) but want to restrict who can see closed loans on a user record to only certain staff.

Proposed solution/stories

  • Links to additional info*

Questions


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