...
...
| Note | ||
|---|---|---|
| ||
This decision has been been archived as it deemed irrelevant based on feedback from the Owner |
Overview
There are several scenarios where modules need a system or tenant-level user. Requirements and various scenarios are captured in
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
- It would be nice if these system/tenant users could be hidden from the users app to reduce the risk of being accidentally changed/removed/etc. It may also be desirable for these to be invisible to librarians to help cut down on clutter in the users app.
- The secret storage design effort may overlap here depending on the approach we take here. See FOLIO secrets management
- Should these users have their own immutable permission sets?
- Shoudl these users have their own immutable patron groups?
- A solution architect (Vasily Gancharov) had started investigating this, but left the project before the work was completed. VBar may know where to find that work. It's unclear how far Vasily got, or if anything helpful exists.
- TBD
JIRAs
Jira Legacy server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-2551
...
|