Customization | Entry 18
Yes. A saved HubSpot record view can be made available to other users so nonprofit staff can work from the same filtered group of records instead of independently rebuilding the same criteria.
A well-governed shared view can establish the correct object, filters, exclusions, date logic, displayed columns, sort order, intended users, and expected action for a recurring group of records.
Sharing turns a useful individual setup into a repeatable organizational resource and can reduce recurring exports to spreadsheets.
A development operations specialist can create and test a donation-level view for completed individual gifts greater than $500 within a rolling three-year period. The team can then use the same definition for stewardship, qualification, campaign planning, and acknowledgment.
This is more reliable than five employees creating five similar views with different date, amount, refund, or donation-status rules.
A saved view shares its filters and display configuration. It does not grant HubSpot access or override object, record, property, or editing permissions. Two colleagues can open the same view and see different records or fields because their underlying access differs.
The exact labels depend on the account interface and the creator's permissions, but current options can include:
| Visibility | Best suited to |
|---|---|
| Private | Personal follow-up, temporary analysis, early testing, or an individual workload |
| My team | A department-owned process that the creator's team needs to access |
| Custom | Selected teams or individual users working across departments |
| Everyone | A genuinely account-wide queue or directory appropriate for every HubSpot user |
Account-wide visibility should not be selected merely because it is convenient. Consider whether the view name, filters, or displayed columns reveal information some staff do not need.
Users can find an accessible shared view, open it as a tab on the appropriate object's index page, reorder it, close it, and reopen it later. Moving a view to the leftmost position generally makes it that user's default view.
Sharing a view does not automatically add it as a tab or make it the default for every recipient. A copied view link can make distribution easier, but the recipient must still be signed into the correct account and have access to the view and its underlying records.
Development | Gifts Over $500 | Rolling Three Years is clearer than Donor List or Final View. A consistent name can identify the responsible team, record group, relevant time period, and intended action.
For every important view, document:
Changing a shared view's filters can affect every colleague who depends on it. Saving changes generally requires the creator or an authorized administrator, subject to the account's current interface and permissions.
Clone a view when teams genuinely need different versions, such as all qualifying gifts for Development and only unassigned qualifying donors for Major Gifts. Uncontrolled cloning can create conflicting definitions, so each copy still needs a clear purpose and owner.
Records generally enter or leave the view as their data changes. A new completed gift can appear, while a refunded gift can become ineligible. A volunteer application can leave an incomplete queue once all requirements are received.
If the nonprofit needs proof of who belonged to a group on a particular date, it may need a static segment, export, campaign association, dated property, reporting snapshot, or external data warehouse.
HubSpot permissions remain the primary access control, but the view should display only what staff need for the task. Review giving amounts, wealth indicators, screening details, program eligibility, financial-assistance status, consent information, confidential notes, and other sensitive columns before sharing.
The exact sharing experience depends on the nonprofit's HubSpot interface, subscription, object, view ownership, permissions, teams, record-access rules, property permissions, sharing configuration, data sensitivity, index-page version, beta enrollment, and governance.
Before promising a shared view, confirm that it has been saved and tested, its visibility reaches the intended users, recipients can access the required records and properties, authorized people can administer it, and its definition and owner are documented. HubSpot's index-page experience continues to evolve, so current sharing labels and controls should be verified during implementation.