Lists App permissions -
- Kathleen Moore
App permissions
Lists app permissions control what functionality within the Lists app a user has access to. App permissions were introduced with the Poppy release.
Lists app permission name | |
|---|---|
| 1 | Lists (Enable): Can view lists |
| 2 | Lists (Edit): Can create, edit, and refresh lists |
| 3 | Lists (Export): Can create, edit, refresh, and export lists |
| 4 | Lists (Delete): Can create, edit, refresh, and delete lists |
| 5 | Lists (Admin): All permissions |
Content permissions
Content permissions limit access to record types in Lists app (and FQM) based on the assigned permission(s) the user already has to view record types in FOLIO. This will help ensure sensitive/confidential data is only available to library staff who must have access to it. Content permissions were introduced in the Ramsons release.
Note: as of the Ramsons release, the user needs all of the listed “get” content permissions for an entity to be able to see that content (e.g. partial content permissions do not provide partial access to that entity in the Lists app; no content for the entity is displayed unless the user has all of the required “get” permissions for that entity).
Record (entity) name in Lists app | Required “get” content permissions | |
|---|---|---|
| 1 | Instances |
|
| 2 | Holdings |
|
| 3 | Items |
|
| 4 | Loans |
|
| 5 | Users |
|
| 6 | Organizations |
|
| 7 | Purchase order lines |
|
Determining access in Lists app
As of the Ramsons release, access will be limited to record types in Lists app (and FQM) based on the assigned permission(s) the user already has to view record types in FOLIO
Changes for end-users (as of Ramsons release):
Limit entity/record types when creating a list based on content permissions
Limit viewing/filtering of lists on the lists landing page based on content permissions
Error/messaging if you don't have permissions for any entity-type
UX Workflows based on content permissions
Scenario | Lists app results (landing page) - Expected outcome | Lists app detail record - Expected outcome | |
|---|---|---|---|
| 1 | The user has all content permissions assigned AND has Lists app permissions assigned
example 1: the user has all “get” content permissions for all record types - Instances, Holdings, Items, Loans, Users, Organizations, Purchase order lines |
example 1: the user has access to lists and filters for all types - Instances, Holdings, Items, Loans, Users, Organizations, Purchase order lines | Note: the user’s Lists app permissions might restrict some of these functions
example 1: the user can create a list for any record type - Instances, Holdings, Items, Loans, Users, Organizations, Purchase order lines |
| 2 | The user does not have all content permissions for each record type AND has Lists app permissions assigned
example 2: the user has all “get” content permissions for Instances, Holdings, and Items, but does not have permissions for any other record type. |
example 2: The user can only see Instance, Holdings, and Item lists and filters. |
example 2: the user can only create new lists for Instance, Holdings, or Item record types |
| 3 | The user has no content “get” permissions assigned AND has a Lists app permission assigned | The Lists app icon appears but the user cannot take any action within the app. In place of the first pane, the following message is displayed in the center of the page: User does not have required permissions. Please contact your system administrator for help. |
|
| 4 | The user has all content “get” type permissions assigned for at least one record type BUT has no Lists app permissions assigned | The user cannot access the Lists app | The user cannot access the Lists app |