| name | use-re-nxt |
| description | How to operate the Blackbaud Raiser's Edge NXT Web View — the browser UI of the nonprofit fundraising CRM. Use this skill whenever an agent needs to DO something inside the Raiser's Edge NXT interface by clicking through pages: finding/adding/editing constituents (donors), entering gifts or gift batches, building lists/queries/reports, working a fundraiser portfolio or opportunities, or just navigating RE NXT. Trigger this whenever the user mentions navigating Raiser's Edge, RE NXT, Blackbaud's fundraising UI, 'in the RE NXT web view', or driving the Raiser's Edge interface with a browser — especially alongside a browser-automation tool. This is for operating the UI; for the REST API integration, use the blackbaud-re-nxt-sky-api skill instead. |
Using Raiser's Edge NXT (Web View)
This skill is the map and playbook for an agent operating the Raiser's Edge NXT (RE NXT) Web View — Blackbaud's browser-based fundraising CRM — by clicking through the UI (typically via a browser-automation tool). It tells you where things are, what each page is for, and the exact sequence of clicks for common tasks, using verbatim button/menu/field labels from Blackbaud's help center.
It pairs with a browser tool: the browser tool supplies the mechanics (click, type, scroll); this skill supplies the domain knowledge (which page, which button, in what order). When you're unsure of a label or layout, prefer what's written here over guessing, and confirm against the live screen.
Operating the UI vs. the API. This skill is for driving the web interface. If the task is a programmatic integration over REST (api.sky.blackbaud.com), use the blackbaud-re-nxt-sky-api skill instead — it's faster and more reliable than clicking for bulk/automated data work.
How to use this skill
SKILL.md is a router. Read the area reference for whatever you're doing — it has the page map and step-by-step playbooks. You rarely need more than one or two at a time.
| If the task involves… | Read |
|---|
| Logging in, the main menu, global search, record-page layout, Work Center, Analysis, the Home page | references/navigation.md |
| Finding/adding/editing constituents; contact info, relationships, notes, actions, codes, custom fields, duplicates, constituent lists | references/constituents.md |
| Entering gifts (one-time, pledge, recurring), gift splits, gift batches, receipting, viewing a donor's giving | references/gifts.md |
| Building/filtering lists, Query, standard reports, exports to CSV, dashboards | references/lists-queries-reports.md |
| Fundraiser portfolios, opportunities (ask/expected/funded, stages), prospect research, fundraiser assignment | references/prospects-opportunities.md |
Start from references/navigation.md if you're not already oriented — every other playbook assumes you can find the main menu, the global search, and a record page.
The mental model in one paragraph
You sign in with a Blackbaud ID and land on either the Home page or the Portfolio › Work Center (depending on role). A persistent left main-navigation menu moves you between areas — Portfolio, Constituents, Gifts, Communications, Events, Analysis, Online giving, Settings. A global search box at the top of every page jumps you to any record. A record opens as one long, scrollable page of collapsible tiles/sections (not tabs) — you scroll and expand rather than click tabs. Most edits happen in modal dialogs launched from an Add or Edit link inside a section.
Cross-cutting UI patterns (true almost everywhere — internalize these)
These cause most mistakes when driving the UI, so keep them in mind regardless of the task:
- Records are long scrolls of tiles, not tabs. To reach Contact information, Relationships, Giving, Actions, etc., scroll down and expand the section — don't hunt for a tab.
- Two-click commit in many dialogs:
Done, then Save. Sub-item dialogs (an address, a phone, a batch row) often commit the item with Done, but the record isn't persisted until you also click Save. Missing the second click silently discards the change.
- Exactly one primary per channel. A constituent must always have exactly one Primary address, one Primary phone, one Primary email. Marking a new one Primary demotes the old one; the first one added becomes primary automatically.
- Heavy operations are asynchronous — watch the notification bell. Exports, query runs, report runs, and gift-batch approvals don't finish on-screen. They run as background jobs and deliver results/download links via the notification (bell) icon in the top nav. After kicking one off, wait and check the bell rather than expecting an immediate result.
- Code-table values must already exist. Dropdown values like constituent codes, relationship types, note types, action types live in Settings › Tables and are admin-configured. If the value you need isn't in the dropdown, it must be added there first — you can't free-type it.
- Web View vs. Database View. RE NXT has two synced interfaces; this skill covers the modern Web View. A few tasks (some query-list edits, custom wealth-rating entry, deleting an opportunity/proposal, deleting a fundraiser assignment) are Database-View-only — the references flag these. When something can't be done in Web View, that's usually why.
- Sync/refresh latency is real. Data isn't instant: edits synced from Database View may need a browser refresh; new gifts can take ~30 min to appear in lists; dashboards lag hours; Home-page tiles update on their own schedules. Don't assume a just-made change is immediately visible.
- Terminology drift (Web vs. Database View). Web Opportunity = Database Proposal; Web Custom fields = Database Attributes; Web Reference field = Database Comments. The navigation was also reorganized ("Navigation Enhancements") — older screenshots may say "Fundraising/Work" where it's now "Portfolio/Work Center." Don't trust stale label memories over the live screen.
- Permissions hide controls. If an Add/Edit/Export option isn't visible, it's usually a rights restriction (and some areas need add-on modules, e.g. Opportunities/prospect research needs Prospect Research Management). Absence of a button ≠ wrong page.
Source of truth
Every page and playbook here is drawn from Blackbaud's official RE NXT help center: https://webfiles-sc1.blackbaud.com/files/support/helpfiles/rex/content/ (static, fetchable help pages). Each reference cites the specific help page per playbook. When the live UI disagrees with this skill, the live UI wins — Blackbaud ships changes — but flag the drift.
