Alma
Your feedback matters to us. Help us improve Alma by telling us what you’d like to see using the message areas below. You can also can support something already posted.
We would love to be able to respond to every idea that is submitted, but this is not feasible. We are, however, committed to responding to the most popular ideas—those that have received the most points.
For more information please review our FAQ and guidelines. Thank you.
29 results found
-
Find and Manage Users by User Group
Add the ability to find and manage users and create user-based sets based on User Group.
499 votesAs part of the Alma July 2020 release “Advanced Search for Users” feature, new search options have been added for searching user records. The option to run advanced searches has also been added. One of the many new search indexes is the User Group.
Search results may be saved as a users set.
For more information, see https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2020/Alma_2020_Release_Notes_Included_Material/2020_RN_07_Main#Advanced_Search_for_Users
-
Ability to run user purge on a set
The current purge job does not allow for granularity beyond the user group and the number of options and filters for the Purge User Records job is very limited.
It would be helpful to be able to run patron purge on a set of user records, or alternatively for Alma to add a user delete job (under Manage Jobs and Sets > Run a Job) that runs on a set.
(see also NERS Request ID 5304)269 votesHi all,
I'm happy to inform you that Alma now allows purging users based on a set. This new option enhances the library's ability to purge users based on varying user record attributes, such as last activity date or expiry date. It is also possible to define a scheduled job. The job is run from the Run a Job page at Admin > Manage Jobs and Sets > Run a Job > Purge Users.
read more in the November 2025 release notes: https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2025/Alma_2025_Release_Notes?mon=202511BASE#:~:text=Purge%20Users%20Based%20on%20Set
Best, Alma Product.
-
Prevent change of fields due to synchronization when running a Update/Notify Users job on a set
When updating one user manually, we get a notice where we can confirm that some fields (amongst others: campus, rs libraries and user group) are not to be overwritten by the next user synchronization.
When updating users in a set running the Update/Notify Users job in Alma, the same choice of prevention is not presented. Hence leaving some fields to be changed back in the next synchronization.
We experienced this running a job changing campus, RS library and user group on a set of users. The first two fields did not change back in the synchronization. The latter did.
Would…
258 votesRunning the Update/Notify Users job with ‘Added/changed field’ set to ‘Internal’ makes the user group/title/campus changes not be overridable by the SIS load.
-
Add functionality to merge patron records when there are duplicate patron records.
The merge should let the user identify the source record and the incoming record, and retain all of the loans, holds and notifications on the incoming record to add to the source record. This way, the remaining record retains all the information from both records, but deletes the incoming record so there aren't any duplicates.
213 votesA user with appropriate privileges can now merge one or more user records into another user record. You can select which segments to merge (contacts, identifiers, notes, blocks, demerits, statistics, attachments and proxy for). All fulfillment activities are merged (loans, requests, fines/fees and interested users) to the new user. To enable this feature, contact Ex Libris customer support.
For more information please see August Release Notes:
https://knowledge.exlibrisgroup.com/Alma/Release_Notes/010_2019/Alma_2019_Release_Notes?mon=201908BASE#merge_patron_records -
Split role user manager in 2: the user manager and the patron manager
Right now any operator at any level with a role enabling the right to edit/delete users in Alma has the rights as well to change or delete roles or scopes of anyone else, even of the Alma administrators (!).
Roles shall be fine tuned in a much more granular way, as to have two separated types of managers and administrators.
- Patron managers shall be enabled to create and edit Patron Users, but not to edit/delete roles assigned to other users, esp. Libray staff Users.
- User administrators instead should be enabled to edit/delete roles of other users, including Library…200 votesAs part of the June release It is possible to restrict users that have access to user accounts so that they cannot update restricted users accounts. For example, it is possible to set that some users that have a User Manager or Circ Desk Operator role will still not be able to update accounts of library staff. Restricted accounts can be defined as accounts with given user groups or with given user roles.
For more information please see Alma Release Notes at: https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2020/Alma_2020_Release_Notes
-
To add the "primary identifier" to the export list of the user set
We would like to add the "primary identifier" to the export list of the user set.
We will use the excel file with "primary identifier" to establish the User set, but not all the primary identifier can be loaded into the user set. So
We would like to add the "primary identifier" to the export list of the user set in order that we could know which primary identifier can not be loaded into the User set.198 votesIt is now possible to include primary identifiers as part of the exported list when using Alma's Export option from the user list. An Extended Export option will generate an Excel file similar to the existing "all fields" export, adding the primary ID as a column.
for more information please see Alma January RN
-
Have the option to send emails to the user’s preferred address or send it to all of the user’s addresses on their account instead.
Sometimes the “preferred addresses” imported from SIS is not the address users frequently uses, they could potentially miss important notifications and cause disputes.
177 votesNow Alma can send emails to multiple recipients simultaneously, for example emails addressed to under-aged patrons can also be sent to their legal guardians. To enable this, Alma now supports a new type of email “CC address” for public and staff type users only. When an email is sent to the patron, it is sent to all of the CC addresses, in addition to the address that is marked as Preferred.
For more information, please see October Release Notes:
https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2021/Alma_2021_Release_Notes?mon=202110BASE -
Add a Preferred Name field to the Alma user record
Alma should have a field, in addition to the first name, for the preferred name.
Our campus allows users to specify a preferred name, for various reasons. And this preferred name is what is used on physical ID cards.
We are working on getting preferred name into Alma, but because there is not a field explicitly available for this data, we'll likely store it in the First name field.
We'd prefer if Preferred name had it's own field, and think this would be a relatively easy change for Ex Libris to make.
175 votesUser Preferred Name is now available as part of Alma February release.
The Alma user profile was expanded to include parameters for a user’s preferred name. The API and SIS options for creating and updating users also include the user’s preferred name. These parameters are indexed and searchable with the Users search option. System notifications and letters that incorporate name information can be updated to use a user’s preferred name. In a future release, display options will be provided.
For more information please see:
https://knowledge.exlibrisgroup.com/Alma/Release_Notes/009_2019/Alma_2019_Release_Notes?mon=201902BASE -
delete users with expired purge date daily with scheduled job
Now deleting users with an expired pruge date has to be done manually and cannot be scheduled with a job. We would like to have a job that can delete these records more easy than now.
ExLibris came with this answer: Alma product management is aware of this issue and most likely scheduling will be possible in future Alma versions. However, there is no specific timeline for this solution, yet. Once the fix is released, information will be included in the relevant release notes and documentation.
It would be an efficiënt addidition in the ALMA jobs.
165 votesHi all,
I'm happy to inform you that Alma now allows purging users based on a set. This new option enhances the library's ability to purge users based on varying user record attributes, such as last activity date or expiry date. It is also possible to define a scheduled job. The job is run from the Run a Job page at Admin > Manage Jobs and Sets > Run a Job > Purge Users.
read more in the November 2025 release notes: https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2025/Alma_2025_Release_Notes?mon=202511BASE#:~:text=Purge%20Users%20Based%20on%20Set
Best, Alma Product.
-
Advanced search option for Users search
Create an advanced search for Users search, just like for physical titles / items. In this search, make it possible to search (for instance) users with specific roles or job categories, identifiers starting with specific prefixes, users with different kinds of blocks, users with outstanding loans or requests, etc, and the possibility to combine these.
128 votesAs of July release you can search for users by combining search criteria, using Alma advanced search. This is available only to users with the roles and privileges to search for users.
For more information please see
https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2020/Alma_2020_Release_Notes -
Implement Just in Time (JIT) SAML provisioning
With Just-in-Time provisioning, you can use a SAML assertion to create users on the fly the first time they try to log in. This eliminates the need to create user accounts in advance from a SIS or FTP file download. Only an authenticated user would be created once validated through the login process. JIT provisioning is common in larger systems like SalesForce.
125 votesYou can now create an Alma user when a user is authenticated with SAML but does not have an existing Alma user. This eliminates the need to create user accounts in advance from a SIS or FTP file download. This option is supported for Primo VE.
For more information please see:
https://knowledge.exlibrisgroup.com/Alma/Release_Notes/010_2019/Alma_2019_Release_Notes#SAML_User_Creation -
New Label "Invoice" for Address Types
We would like to have the possibility to choose a specific label "Invoice" as address type. This would be used for institutional accounts as some of them have an additional Invoice address which is different than the "Home" one. Having such a label could be used for harvesting data to an external billing application.
Thank you very much!108 votes -
Remove notices from patron accounts
We try so hard to anonymize. It would be nice to be able to purge patron "attachments" after a certain amount of time.
96 votes -
Disable autofill for fields in user details screen
It is apparently possible to mark fields to not allow autofill: https://stackoverflow.com/questions/40200130/how-to-disable-chrome-to-autofill-username-email-password/40200269#40200269
This is what should be done for the fields on the user management screen that cause issues. Specifically the Primary identifier and Pin fields:
https://www.screencast.com/t/SJ91zBqdIfkThese fields would seldom if ever, need to be filled with the Alma employee users saved info.
The current suggestion of just turning off autofill for the browser is not adequate:
https://knowledge.exlibrisgroup.com/Alma/Knowledge_Articles/PIN_number_letter_sent_to_patron_although_PIN_number_was_not_changed83 votesThis was identified as a defect that was resolved as part of Alma July release
-
Add City and NPA from physical address to global Contact Information screen of user
When you consult the Contact Information Tab of a user, you can only see the first line of the physical address, which most of the time is the street address.
We would like to add the column City and NPA to this screen.This way, for over 90% of our patrons, we can directly see the complete address without having to consult the detail of the address.
This would save us much time, as staff are required to regularly ask the patrons whether their address is still correct.
77 votesThe City and Postal Code from a user’s physical address are now visible in the Contact Information page.
For more information see Alma May Release Note at:
https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2020/Alma_2020_Release_Notes -
Add the Import function to the Statistical Categories/Types mapping table.
Statistical Category and Category Types can be Imported but mapping them is exceedingly tedious.
44 votes -
Customize gender description for NONE
We would like to be able to customize the gender field to change the description for the code NONE.
Australian legislation now requires the University to supporting the following in capturing gender data:
"18. Where sex and/or gender information is collected and recorded in a personal record, individuals should be given the option to select M (male), F (female) or X (Indeterminate/Intersex/Unspecified)." -- http://www.ag.gov.au/Publications/Documents/AustralianGovernmentGuidelinesontheRecognitionofSexandGender/AustralianGovernmentGuidelinesontheRecognitionofSexandGender.doc
The existing description is hard-coded and uses the term "None'. EL advised us to use the code NONE for this purpose. However the description is not appropriate for describing people who do not identify as either…
41 votesAs of July release institutions can change the values of the list of user genders to conform with their local legislation.
for more information please see Alma July release notes:
https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2021/Alma_2021_Release_Notes#Customization_of_the_Genders_Code_Table -
Existing linked accounts need active lookup to update patron expiration date
In a consortium with shared circulation policies and privileges, linked accounts need an active lookup each time they are used so that expiration dates that may have changed since a user record was first brought into an institution other than their own, can be updated to ensure a user is still entitled to privileges at another institution.
We understand that the Alma Roadmap includes plans to bring blocks through on linked accounts using a network level block, but expiration dates are also important once a linked account is already created and is used again.
33 votes -
View only administrator role
The administrator role may be helpful to get a full overview of the configuration and possibilities of Alma. However, this role can have far-reaching consequences and should not be given to anyone.
A "View only" administrator role would be helpful for local Alma project group members to get access to the whole config, with no risk of modifying/deleting the configuration.22 votes -
Resource Sharing library field as mandatory for user records
We would like to configure Resource Sharing library field as mandatory for (at least public) user records by having a "Resource Sharing Library" line in the drop-down in Public/Staff User Mandatory Fields table.
Additionally, it could also be interesting to allow creating user registration rules for the "Resource Sharing Library" field.18 votes
- Don't see your idea?