Customization | Entry 12
Yes. HubSpot record pages can be customized to show the properties, activities, associations, reports, and actions that matter most to the people using them. The goal is to help each team understand the relationship and take the appropriate next action without searching through every field or opening several systems.
A nonprofit can organize constituent, household, donation, volunteer, membership, program, company, and other records around the work its staff actually perform. The same constituent record remains the source of truth, but different teams can prioritize different context.
A development officer may need lifetime giving, household information, and stewardship tasks near the top. A volunteer coordinator may instead prioritize skills, availability, training, background-check status, assignments, and hours served.
Identifying information, important properties, grouped property cards, and common actions such as notes, emails, calls, tasks, and meetings.
The activity timeline, Overview, custom tabs, reports, summaries, app cards, stage trackers, and other supported context.
Associated records, selected details, association labels, relationship status, and options to preview or open related records.
One person may be a donor, volunteer, member, event attendee, program participant, board member, corporate contact, newsletter subscriber, or family member of another constituent. A record designed for only one department can hide context that another team needs.
Maya Santos is a monthly donor, volunteer, member, recent event attendee, and board member at a partner organization. Her record can organize one shared relationship in ways that support different teams.
Available hierEligible Professional and Enterprise accounts can create team-specific record views. A development team might prioritize giving and stewardship, while program staff see eligibility, enrollment, attendance, outcomes, and service relationships. Leadership may receive a concise summary instead of every field and activity.
The purpose is not to hide necessary information arbitrarily. It is to make the record easier to interpret for each team's responsibilities.
Yes, supported cards can be displayed conditionally based on property criteria. This can reduce clutter and bring the appropriate information forward at the right time.
It is the view that makes the most important information easy to find and act on. Before adding a field, card, report, or association, ask who needs it, what decision it supports, how often it is used, whether it is sensitive, and whether the data is reliable enough to display prominently.
Customization cannot correct poorly structured or unreliable data. A beautifully organized record will still mislead staff if properties are incomplete, associations are incorrect, or integrations are not updating properly.
When native cards do not cover a nonprofit process, custom or app-provided cards can display selected external information or add supported actions to a record. This might include donation-platform information, event attendance, volunteer schedules, advocacy activity, program data, grant deadlines, or external payment status.
An app card does not necessarily store its data in HubSpot or make that data available to every report and workflow. Confirm whether the integration displays or synchronizes information, respects permissions, supports reporting and automation, and requires a separate subscription or usage credits.
Available customization depends on the HubSpot subscription, object type, seat, permissions, team configuration, installed apps, card type, and data model. Before implementation, confirm:
HubSpot's exact record-layout features and limits can change. Confirm current subscription requirements, supported card locations, tab and card limits, and personalization controls before implementation.