1 App permissions
- 1.1 Poppy & Ramsons
- 1.2 Sunflower roles:
- 1.3 Trillium roles:
2 Content permissions
- 2.1 Content permissions per flower release:
3 Determining access in Lists app
- 3.1 UX Workflows based on content permissions

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, and Eureka capabilities were introduced in the Ramsons release.

Poppy & Ramsons

	Lists app permission name (OKAPI)	Lists app capability (Eureka)

	Lists app permission name (OKAPI)	Lists app capability (Eureka)
1	Lists (Enable): Can view lists	resource: Module Lists Enabled action: view
2	Lists (Edit): Can create, edit, and refresh lists	resource: Module Lists Refresh action: view
3	Lists (Export): Can create, edit, refresh, and export lists	resource: Module Lists Export action: view
4	Lists (Delete): Can create, edit, refresh, and delete lists	resource: Module Lists action: delete
5	Lists (Admin): All permissions	resource: Module Lists action: manage

Sunflower roles:

	Functionality	Application	Capability sets - Settings

	Functionality	Application	Capability sets - Settings
1	View: Can view lists	app-fqm	resource: Module Lists Enabled action: view
2	Edit: Can create, edit, and refresh lists	app-fqm	resource: Module Lists Refresh action: view
3	Export: Can create, edit, refresh, and export lists	app-fqm	resource: Module Lists Export action: view
4	Delete: Can create, edit, refresh, and delete lists	app-fqm	resource: Module Lists action: delete
5	Admin: All permissions	app-fqm	resource: Module Lists action: manage

Trillium roles:

The following capabilities/capability sets determine what functionality within the Lists app a user has access to. The following can be used to create authorization roles.

	Functionality	Application	Capability sets - Settings

	Functionality	Application	Capability sets - Settings
1	View: Can view lists	app-lists	resource: Module Lists Enabled action: view
2	Edit: Can create, edit, and refresh lists	app-lists	resource: Module Lists Refresh action: view
3	Export: Can create, edit, refresh, and export lists	app-lists	resource: Module Lists Export action: view
4	Delete: Can create, edit, refresh, and delete lists	app-lists	resource: Module Lists action: delete
5	Admin: All permissions	app-lists	resource: Module Lists action: manage

Note: when using these settings to create a role, the system will automatically select additional capabilities/capability sets that are inherited/required; this is expected behavior. See the recording below for an example.

Overview of Lists app role creation in Trillium release

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).

Content permissions per flower release:

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

App permissions + Content permissions determine what access a user has in Lists

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

	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*	Record type filter - Show all entity types Visibility filter - show shared and private lists (of that user): for all entity types Status filter - show active and inactive lists: for all entity types 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 Create a new list - Record type selection - All entity types are displayed Edit a list: no change Export a list: no change Duplicate a list: no change Delete a list: no change Refresh a list: no change Show columns: no change 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.*	Record type filter - only show entity types the user has all “get” content permissions for Visibility filter - show shared and private lists (of that user) for: only the entity types the user has all “get” content permissions for Status filter - show active and inactive lists for: only the entity types the user has all “get” content permissions for example 2: The user can only see Instance, Holdings, and Item lists and filters.	Create a new list - Record type selection - only show entity types the user has all “get” content permissions for Edit a list: no change Export a list: no change Duplicate a list: no change Delete a list: no change Refresh a list: no change Show columns: no change 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.	The user cannot take any action on a detail record In the event the user tries to navigate directly to the URL for a list (they have it saved, or someone sends it to them) - the user gets an error message “You don’t have access to this app/record”
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

Lists App permissions