Users App (UXPROD-784)

[UXPROD-37] Limit/scope for permission assignments Created: 18/Jan/18  Updated: 01/Dec/23  Resolved: 01/Dec/23

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Users App

Type: New Feature Priority: P4
Reporter: Cate Boerema (Inactive) Assignee: Amelia Sutton
Resolution: Won't Do Votes: 0
Labels: usermanagement
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by UXPROD-269 CRUD service points Closed
Epic Link: Users App
Analysis Estimator: Khalilah Gambrell
Front End Estimate: Small < 3 days
Front End Estimator: Jakub Skoczen
Back End Estimate: Large < 10 days
Back End Estimator: Jakub Skoczen
PO Rank: 26
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R2
Rank: FLO (MVP Sum 2020): R5
Rank: GBV (MVP Sum 2020): R2
Rank: Grand Valley (Full Sum 2021): R4
Rank: hbz (TBD): R2
Rank: Hungary (MVP End 2020): R2
Rank: Lehigh (MVP Summer 2020): R4
Rank: Leipzig (Full TBD): R4
Rank: Mainz (Full TBD): R4
Rank: TAMU (MVP Jan 2021): R4
Rank: U of AL (MVP Oct 2020): R2

 Description   

Not sure if this is v1 or not. Some permissions should only be given to a user within the context of a service point (e.g. a circ desk) or a location. Kimie has done some initial mockups showing how permission assignment limits might looks which need to be discussed with UM and RA.

https://drive.google.com/file/d/16mjg03A031g-an50ZBWsNIe_WWFLnNie/view?usp=sharing

RA SIG (April 5, 2018): There was also some further discussion as to whether we need to support limiting the scope of a FOLIO operator's permission by service point. Apparently this is something systems offer, but it didn't seem like a top priority to the RA SIG and we need to have more conversations with other SIGs about permission scope limits and what is really needed. We might end up doing permission scope limiting by locations instead (or some component of a location like libraries).

Purposes:
Limit staff to different types of work at different libraries and service points
Examples:

  • student workers who's roles have different limitations at different locations
  • cross departmental library staff who's roles have different limitations at different locations
  • technical/public services staff who need to be able to perform functions only from specific locations e.g. technical sevices staff need to only be able to check out materials that are in cataloging


 Comments   
Comment by Erin Nettifee [ 23/May/23 ]

Dennis Bridges - does this make sense to look at in the context of consortia support work? If not, it probably should be closed at this point as "Won't do" Amelia Sutton

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