Customization | Entry 17
Yes. HubSpot saved views give nonprofit teams reusable tables of contacts, households, donations, memberships, volunteer records, program enrollments, grants, and other CRM records. A view can preserve filters, columns, sorting, and sharing settings. Authorized users can also select records in the view and perform supported bulk actions.
A saved view displays all records or a filtered subset of records on an object's index page. Instead of rebuilding the same search every time, staff can open an agreed workspace for recurring tasks.
Each row represents a record. The columns show selected properties that help staff understand and manage those records.
SYBUNT generally means Some Year But Unfortunately Not This Year. A development team can use this view to identify households that gave in a previous year but have not yet given during the current year.
The filters might require prior-year giving greater than zero, current-year giving equal to zero, an active household status, and appropriate do-not-contact and deceased-household exclusions.
A household-level giving view may rely on donation records, correct household associations, association labels, rollups, calculated properties, workflows, custom code, or a fundraising integration. If refunds, canceled gifts, soft credits, or offline gifts are handled inconsistently, a clean-looking table can still be wrong.
Every saved view belongs to one object. The team must decide whether it needs one row per person, household, donation, membership, enrollment, grant, or another record type.
| Question | Likely starting object |
|---|---|
| Which households have not given this year? | Household |
| Which individual gifts exceeded $500? | Donation or transaction |
| Which donors made a qualifying gift? | Contact or household, with suitable rollups |
| Which memberships expire next month? | Membership |
| Which grants have reports due soon? | Grant |
Choosing the wrong object can create duplicate rows, miss qualifying records, produce incorrect totals, or apply a bulk update to the wrong type of record.
Filters define which records appear. Columns determine what staff can understand and do once those records are visible. A useful shared view should include only the properties needed for the decision or task.
For example, Development | SYBUNT Households | Current Year is clearer than Donor List 2. Strong naming reduces duplicate views and helps staff recognize the authoritative version.
Depending on access, a saved view may be private, shared with a team or selected users, or available to everyone. Private views suit personal workloads, temporary analysis, or filter testing. Shared views give a team one agreed definition, common columns, and a dependable queue of records.
Frequently used views can remain open as tabs. Users can rearrange those tabs and move a view to the leftmost position to make it their default for that object.
Authorized staff may be able to select records and assign an owner, update a property, create tasks, or perform another supported object-specific action. The exact options depend on the object, subscription, permissions, and current interface.
A bulk edit changes only the selected records. Matching the view does not automatically mean a record has been selected.
A day-to-day table staff can open, review, and work from.
A reusable group that can support other HubSpot tools, depending on subscription and object eligibility.
A summary, comparison, or visualization that helps the team understand performance and trends.
A fixed record of group membership at a particular time. A saved view is usually live, so records can enter or leave as their properties change.
Saving every filter anyone has ever used can create duplicate definitions, outdated criteria, unclear ownership, and unreliable work queues. Shared views should be governed like other operational tools.
A shared view does not replace HubSpot's underlying record and property permissions.
The exact saved-view experience depends on the nonprofit's subscription, object, account configuration, permissions, view ownership, sharing settings, properties, associations, custom or app objects, automation, installed applications, record count, and current HubSpot interface.
Before promising a view, confirm that the required object and properties exist, the data is stored consistently, historical conditions can be represented accurately, associated data has been rolled up when needed, the desired bulk action is supported, and the update will not trigger unwanted automation.