General Feature Requests

Right now the search functionality within the admin side of the site (seems to require) exact matches, and doesn't allow for missing info within a search term. If you have a constituent named Joseph Arnold Jay, a search for "Joseph Jay" won't show them. The ideal would be for us to have fuzzy search so that it was typo tolerant, ideal++ would be full semantic search. Even standard BM25 search would be an improvement because it would catch Joseph Arnold Jay with the query "Joseph Jay."

In March of 2026, Almabase interviewed the Alumni Engagement director at University of Illinois. One of her big points she made was that it is CRITICAL to remove barriers to register for evemts if you want to increase engagement. We need the abililty for an allum to enter their first and last name and year into the registration section of an event at the beginning and have almabase look for a match - the same way it works now on the back end when you go to map a registrant for an event. That is, have the registrant REVIEW their info vs. RE-KEY their info! This is so basic in terms of "we know you" and would go a long way to (1) reducing hte time it takes to register for an event AND (2) help us keep people engaged - make it easier to registe, and (3) cut down on "verification emails" because people enter a new email and (4) cut down on abandonment + drop ins. This should be optional when an admin is setting up an event. Some institutions obviously have large bases and they many not want this. But we have less than 5,000 alums and they are all in Almabase, so we really want this. I mean this is a DIRECT suggestion from the interviewee more than 6 months ago and it's still not on the roadmap as far as I can tell.

We use Almabase to engage multiple constituent audiences, including alumni, parents, students, and donors. Not every constituent group should have the same visibility in the online directory. It would be helpful to have the ability to create automated directory visibility rules based on data synced from Raiser's Edge NXT, such as constituent codes, categories, attributes, or other mapped fields. For example, administrators could define rules that automatically: Show certain constituent groups in the directory Hide other constituent groups from the directory Apply these settings during imports and ongoing syncs Currently, directory visibility often requires manual updates after data imports, creating additional administrative work and increasing the potential for errors.

We often have a single event, with a larger multi-ticket event, that has multiple ticket types. It would be helpful to be able to send a single reminder/logistics email (or other communications) to all registrants within the different ticket types at once - multi-selection of specific sub-events would make this process much more efficient.

We sometimes find that email addresses don't actually belong to the constituent record it is attached to (for example a parent email on a student record or reverse). For these in Raiser's Edge, we change the email type to one that indicates it is a bad email instead of adding a solicit code so in case we do receive an updated email address communications could continue. It would be nice if in Almabase Data Studio we could filter on email type so that those can be taken out of communication lists since a solicit code wouldn't be appropriate in this case.

Please add a field to the tribute section for online gifts for who to notify about gifts made in memory or in honor of someone.

Need a separate permission to edit directories. Currently can only do this as a Site Admin.

Right now Access Control to features like the Directory are restrictive, and having any restricted affiliation makes you unable to access that feature. Entitlements based "Alumni may access X" is a more common way of handling this, and makes more sense. This is also how other parts of the product function (such as Spaces) - going to entitlement only would unify the permissions systems. Verified Groups provide an sensible way of doing this. This has been previously discussed in: https://almabase.canny.io/digital-engagement/p/give-directory-access-based-on-matching-permissions https://almabase.canny.io/feature-requests/p/update-access-permissions-to-user-directory I'm submitting this as a separate request because the feature request is different. tl;dr: Entitlements, not restrictions, and using the Verified Groups system.

There are a couple of upgrades to the invitees tab in the event module which would greatly improve the administration of events communications. 1.) the ability to see the communication group name once it has been uploaded/added to the invitee tab. 2.) the ability to bulk remove an uploaded/added communication group (list) in it's entirety after it has been attached to the event 3.) the ability to bulk remove selected individuals once a communication group has been uploaded/added to the event (as opposed to clicking into each person and removing them one by one. These upgrades would allow for several key facets of events management when there are review processes/workflows in place. 1.) it will allow for easy review/approval of events by senior admins/managers if another staff member is working on building out an event. Admins/Managers can confirm the correct communication group has been added before approving the invitation for deployment. 2.) Occasionally, after a group has been put together, a late review comes in and certain segments needs to be removed. It would be beneficial for team managers to be able to bulk remove those individuals without having to do them individually OR having to reach out to Almabase support and ask them to remove them.

For example, a group at a school is looking for a speaker on a specific topic - they can create a public facing post that any individual can click and express interest in volunteering.