Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-37

Limit/scope for permission assignments

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Open (View Workflow)
    • Priority: P4
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Template:
      UXPROD features
    • Epic Link:
    • Front End Estimate:
      Small < 3 days
    • Back End Estimate:
      Large < 10 days
    • Development Team:
      Prokopovych
    • Calculated Total Rank:
      33
    • 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

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                pwanninger Patty Wanninger
                Reporter:
                cboerema Cate Boerema
                Analysis Estimator:
                Khalilah Gambrell Khalilah Gambrell
                Front End Estimator:
                Jakub Skoczen Jakub Skoczen
                Back End Estimator:
                Jakub Skoczen Jakub Skoczen
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases