How are users with multiple affiliations supported with respect to authentication, permissions, etc.?
Institutions’ user lists are loaded separately. A user who is a graduate student at institution A and staff at B will be loaded in two separate feeds into two separate Alma user management systems – as graduate patron at institution A and staff at institution B.
There is no link in the system between these two records. In other words, the same patron when requesting fulfillment services from institution A will be identified as a graduate student and when requesting fulfillment services from institution B will be identified as a staff.
Future plans for Alma enable the two feeds to include a consortially unique ID that will enable Alma to link the institution A and institution B records. Still, fulfillment services at each institution will be applied as per the patron attributes that have been loaded into that same institution.
Access to system screens and data is controlled by Alma roles, which are assigned to users in Alma. Each role allows its owner access to specific actions and data in the system. The roles may also be controlled by scope, in a manner that allows its owner access to data and workflows only in the context of the specific libraries. For example, an operator may be granted a role of ‘Purchasing Operator’ in the scope of Library A, which will result in being able to process acquisitions purchase orders only for Library A. The users’ roles and scopes are managed by an Alma user who is given a “User Manager” role.