Managing Rialto User Roles
- User Manager
- User Administrator
The user roles below are required to access Rialto functions
- These roles become available in the system only when Rialto Acquisitions or Workflows are enabled in Alma for your institution.
- The Rialto Purchaser role has replaced the Alma Purchasing Operator role. Purchasing Operator is no longer required to perform Rialto functions.
- Rialto Search accounts do not have Rialto roles. For information about Rialto Search (available on all Alma instances that do not have Rialto Acquisitions) please see Rialto Search documentation.
- As of November 2020, the Alma Selector role was repurposed solely for Rialto use. Thus, there may be existing users in your system that have this role, and they will automatically have access to Rialto once it is enabled.
For a comprehensive list of Alma user roles, see Managing User Roles.
For information, watch the Rialto Quick Start video (2:42 min). This video includes information on Rialto user roles.
Rialto User Roles – Descriptions and Accessible Components
User roles determine not only which pages a user can access, but also the fields that appear or actions that the user can perform on these pages.
The following table describes the Rialto roles that can be assigned to users and the privileges that each user role includes. For more information about the activities that can be performed per page, please consult the respective pages in the documentation.
| Module | Role | Privileges | Description | Scope |
|---|---|---|---|---|
|
Rialto Acquisitions
|
Shared across all Rialto roles excluding: Faculty, Rialto Search, and the Collection Development Manager role
|
|
Upon Rialto enablement, most user roles can perform basic system actions, such as searching the market, and adding titles to a list.
Rialto includes several out-of-the-box feeds, and most users can modify their own view of these feeds.
Most users also have read only access to applicable system displays such as the DDA pool and Selection Plan results.
Most users are able to view information relative to validating an interested user on an order.
|
Institution
|
|
Faculty
|
This is the only Rialto role that does not include search.
|
This role is added to a faculty user when a librarian shares a Title Alert with them. It enables the faculty member to access the shared Title Alert within Rialto directly to make a recommendation. If needed, they can add an interested user or internal note. For more information, see Faculty Title Alerts.
|
Institution | |
|
Rialto Search
|
|
The Rialto Search role is intended for users who need to discover and evaluate resources in the Rialto marketplace without participating in other workflows.
Although the Rialto Search role can be assigned together with any other Rialto role, this is generally not recommended. Other Rialto roles include the same search capabilities, together with additional permissions, making the Rialto Search role primarily suitable as a standalone role.
|
Institution/Library
|
|
|
Selector Limited
|
|
Users with the Selector Limited role focus on evaluating and selecting new titles in the marketplace. They can manage purchase requests and have view access to Alma acquisition data.
This role enables users to submit offers in their cart to acquisitions for approval.
This role contains baseline Alma privileges, principally for managing purchase requests and viewing acquisitions data. For a comprehensive list of privileges, see Role Privileges.
|
Institution / Library
|
|
|
Selector
|
|
Users with the Selector role focus on evaluating and selecting new titles in the marketplace. They can manage purchase requests and have view access to Alma acquisition data. Additionally, they can add to the DDA pool, pin EBA titles, and manage their own (or shared) title alerts.
This role enables users to submit offers in their cart to acquisitions for approval.
This role contains baseline Alma privileges, principally for managing purchase requests and viewing acquisitions data. For a comprehensive list of privileges, see Managing User Roles.
|
Institution / Library
|
|
|
Super Selector
|
|
The Super Selector role enables users to manage recommendation and ranking profiles, manually add to the DDA pool, pin EBA titles, and manage their own (or shared) title alerts.
Because they cannot manage purchase requests or view acquisitions data, this role is generally added to a user in combination with another role.
|
Institution / Library
|
|
|
Rialto Purchaser
|
|
Rialto Purchasers may submit orders without approval, manually add titles to the DDA pool, and pin titles in the EBA pool.
Rialto Purchasers can also submit the cart for approval (like the Selector user roles), though this additional configuration is disabled by default. If your workflow requires purchasers to also submit orders for approval, contact Customer Support.
|
Institution/Library
|
|
|
Rialto Manager |
|
Rialto Managers can approve orders submitted by other staff in Rialto. They are also able to submit orders to Ex Libris for purchase, to manage recommendation and ranking profiles, manually add to the DDA pool, pin EBA titles, and manage their own (or shared) title alerts. Because they cannot view or edit Alma acquisitions data, this role is typically paired with Purchasing Operator.
|
Institution / Library |
|
|
Rialto Administrator
|
|
Rialto administrators are responsible for configuring Rialto. They can manage recommendation and ranking profiles, selection plans, and EBA programs, as well as any institutional cart defaults or required fields.
As with other Rialto roles, admins can also manage their own (or shared) title alerts.
Rialto administrators cannot submit orders. If this action is needed, pair with Rialto Purchaser.
|
Institution
|
|
|
Rialto Workflows
|
Collection Development Manager |
|
Collection development managers are responsible for running collection development workflows in Rialto. They are the only users who can access the Workflows menu under Collection Development and perform all project-level actions, from creating projects to generating and reviewing recommendations.
Collection Development Managers do not configure collection development settings. Configuration tasks are the responsibility of Repository Administrators and Rialto Administrators (these roles do not have access to the workflows themselves).
|
|
|
Miscellaneous
|
Chat with Support
|
|
Enables staff users to open chat sessions with our Support Team. For more details, see Online Chat Support for Rialto.
|
Institution
|
Staff who only have Rialto roles assigned to them are not counted against the Named User Report in Alma.

