[UXPROD-3916] Support limiting acquisition unit ("teams") membership by geolocation (geofencing) Created: 07/Dec/22  Updated: 30/Nov/23

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

Type: New Feature Priority: TBD
Reporter: Brooks Travis Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: acquisition-units, back-end, front-end, okapi, security, security-reviewed, stripes, teams
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
clones UXPROD-3915 Support limiting applicable permissio... Draft
Potential Workaround: Multiple user accounts for each operator based on service point access
Development Team: None
PO Rank: 0
Rank: Cornell (Full Sum 2021): R5

 Description   

Current situation or problem:

FOLIO currently supports assigning users to acquisition units (maybe "teams" in the future). Users are then able to act in the context of that unit/team from anywhere. However, it is desirable to be able to limit certain applicability of a  unit/team assignment to a particular geolocation, determined by some geolocation mechanism (eg. IP address, device location/GPS, installed browser certificate, SAML assertion, etc.)

In scope

  • A mechanism to configure geofences for acq units/teams
  • A mechanism to determine the geolocation of a FOLIO user during acq unit/team membership resolution
  • Only resolve units/teams without geolocation restriction or that are restricted to the current geolocation

Out of scope

  • Anything to do with limiting service points by geolocation
  • Anything to do with limiting permissions by geolocation

Use case(s)

Proposed solution/stories

Links to additional info

Questions



 Comments   
Comment by Axel Dörrer [ 08/Dec/22 ]

Brooks Travis Do you want the security team to weigh in? If so please reach out, thanks.

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