Issues
- Support limiting acquisition unit ("teams") membership by geolocation (geofencing)UXPROD-3916
- Support limiting applicable permissions by geolocation (geofencing)UXPROD-3915
- Upgrade Stripes to version 3.0.0UIPFIMP-14Resolved issue: UIPFIMP-14Taras Tkachenko
- On small screens the action menu is covered by the headerUINV-374Resolved issue: UINV-374Dennis Bridges
- Upgrade Stripes to version 3.0.0UIDATIMP-422Resolved issue: UIDATIMP-422Taras Tkachenko
- Remove and archive react-githubish-mentionsSTRWEB-41Resolved issue: STRWEB-41Zak Burke
- Addition of Tabs component to stripes-componentsSTCOM-922Andrew Isherwood
- Add possibility to pass one more prop with unique prefix for column header id'sSTCOM-767Resolved issue: STCOM-767John Coburn
8 of 8
Support limiting acquisition unit ("teams") membership by geolocation (geofencing)
Description
Priority
TBDFix versions
None
Development Team
None
Assignee
Unassigned
UnassignedSolution Architect
None
NoneParent
None
Parent Field Value
None
Parent Status
None
Checklist
hideTestRail: Results
Details
Reporter
Brooks TravisBrooks TravisPotential Workaround
Multiple user accounts for each operator based on service point accessPO Rank
0Rank: Cornell (Full Sum 2021)
R5TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Reporter
Brooks Travis
Brooks Travis
Potential Workaround
Multiple user accounts for each operator based on service point access
PO Rank
0
Rank: Cornell (Full Sum 2021)
R5
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created December 7, 2022 at 3:53 PM
Updated November 30, 2023 at 4:41 PM
Activity
Show:
Axel DörrerDecember 8, 2022 at 4:18 PM
@Brooks Travis Do you want the security team to weigh in? If so please reach out, thanks.
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