Altru is hard to learn by clicking around. It covers admissions, memberships, fundraising, events, retail, and reporting, and those areas share the same constituent records underneath. New users usually get stuck because nobody explained how the pieces connect, not because any one screen is complicated.
This is the order we’d suggest to a new coordinator, registrar, or development associate in their first month. It starts with the ideas everything else depends on, then moves to the work your role actually does.
Start with the data model, not the menus
Before you learn any task, get comfortable with four ideas. Almost every “why did it do that?” moment traces back to one of them.
- Constituents. Every person and organization is a constituent record. Tickets, memberships, gifts, and event registrations all hang off that record. If a guest has two records, their history is split in two, and the problems start there.
- Households. Individuals can be grouped into households, which affects how memberships, mailings, and recognition work. Find out how your organization uses households before you create or merge anyone.
- Revenue. A sale at the front desk, a web purchase, a membership, and a donation all end up as revenue tied to a constituent (or to an anonymous sale). Knowing where revenue lands makes reports far less mysterious.
- Configuration vs. transactions. Much of Altru’s behavior is set in configuration: membership programs, price types, programs and events, designations. Transactions follow those rules. When something looks wrong, ask whether it’s the transaction or the setup behind it.
Learn your own role first
Nobody needs all of Altru on day one. Pick the area you’ll use daily and learn it well before branching out.
Front desk and admissions
Focus on daily sales, looking up a constituent, selling to a member, handling a refund or exchange, and the end-of-day reconciliation steps your organization follows. Then learn advance sales for timed tickets and how capacity works for your programs.
Membership
Learn how your membership programs are set up: levels, terms, renewal and lapse rules, and how cards are issued. Then practice joins, renewals, upgrades, and gift memberships until you can predict the expiration date before you save.
Development and finance
Start with recording gifts, batches, designations, and acknowledgments. Then learn how revenue reaches your general ledger, or whatever export your finance team relies on. Ask finance what they need from you before you change how anything is coded.
Group sales and education
Learn group sales reservations, deposits and balances, itinerary details, and how a booking turns into revenue when the group arrives.
Then learn queries
Queries are where Altru users go from “I can do my job” to “I can answer questions.” Most lists, exports, mailings, and many custom reports start as a query. Learn the difference between ad-hoc queries and selections, how to filter on dates and memberships, and how to choose output fields. Build small ones first, such as “members expiring next month” or “people who bought tickets last weekend,” and compare the counts against something you already know.
Smart fields are worth learning next. They store calculated values on records, like lifetime giving, so queries and reports don’t have to recalculate them every time.
Where to actually learn
- Blackbaud’s own training and help. Blackbaud offers online help documentation and training courses for Altru, including introductory material for new users. What’s included varies by subscription, so ask whoever manages your Blackbaud account which courses you have access to, and start with the fundamentals.
- Your organization’s documentation. Ask for written procedures, even rough ones. If none exist, start a document as you learn and share it with your team.
- A colleague who has been there a while. Shadow a full shift or a month-end close. You’ll learn local conventions, such as naming patterns, which price types to use, and which reports leadership reads, that no generic course can teach.
- The Blackbaud community. Other Altru administrators post questions and answers in Blackbaud’s online community. Searching there before you open a support case often saves time.
- Blackbaud support. When you’re unsure whether something is a bug, a setting, or expected behavior, ask support. Don’t guess on anything that changes financial data.
Practice somewhere safe
Find out whether your organization has a sandbox or test environment. If it does, use it for anything you haven’t done before, especially merges, refunds, batch commits, and configuration changes. If it doesn’t, practice on a test constituent your team agrees on, and never on a real member’s record.
Some actions are hard to undo cleanly. Merging two constituents and committing a batch are common examples. Learn those with someone watching the first few times.
Habits that keep the database healthy
- Search before you create. Look up a guest by email, phone, and last name before adding a new record. Duplicate records are one of the most common long-term data problems in any constituent database, and they are much easier to prevent than to clean up.
- Use the fields the way your organization does. Free-text notes are fine, but information that belongs in a structured field should go there, or queries won’t find it.
- Write down what you changed and why. A short note on a record or in a shared log saves the next person an hour.
- Ask about config before you touch it. One edit to a membership program or price type affects every future transaction that uses it.
A realistic first-month goal
By the end of your first month, aim to handle the everyday transactions for your role without help, find any constituent and read their history, build a simple query and export the results, and know who to ask (internally or at Blackbaud) when something doesn’t behave the way you expect. Reporting, configuration, and the rest of Altru can come later, once that foundation is solid.
