Architecture | Entry 7 of 11
Yes. HubSpot record pages can display records associated with the person, organization, donation, household, volunteer activity, membership, event, program, or other record being viewed. Staff get a connected view of the relationship and can open relevant records without repeatedly searching the CRM.
HubSpot stores different types of information in separate objects and records. Associations connect those records, while the record-page layout helps staff see and use the connections.
For example, a contact record may display associated records for:
A staff member can select an associated record to review its properties, activity, and relationships. This makes it easier to move through the constituent's story while keeping each type of information in the appropriate record.
Administrators can configure supported record layouts and association cards so the most useful information appears for staff. Available customization depends on the account's HubSpot products, subscription, permissions, and object setup.
A constituent's value to a nonprofit is rarely captured by one role or transaction. The same person may donate, volunteer, attend events, belong to a household, work for a corporate sponsor, participate in a program, or hold a membership.
Visible associated records help teams:
When those relationships are disconnected, each team sees only part of the person’s history. Associations bring the details together while keeping every record type organized.
This supports clearer constituent histories, better staff coordination, stronger segmentation, more accurate reporting, useful workflow automation, and fewer disconnected records.
A nonprofit has a contact record for Maya. From her record, authorized staff can see:
A development employee opens Maya's contact record before a call. They can see that she recently registered for the gala and that her household increased its recurring gift. They open the household record to understand collective giving, then the company record to review sponsorship history.
The employee does not need to search for each record separately or ask another department for context. The relationships are visible from the record they already use.
A well-designed record page cannot compensate for missing associations, duplicate records, unclear object purposes, or inconsistent data-entry practices.
Before configuring the record layout, decide:
The layout should make the nonprofit's architecture easier to use, rather than expose every possible record simply because it exists.
The information shown on a HubSpot record depends on the object, record layout, association configuration, user permissions, subscription, and connected applications.
Before implementation, confirm:
Team-specific preview customization requires an eligible Professional or Enterprise subscription, and users need the appropriate administrative permission to customize it. The exact setup should be confirmed for the nonprofit's HubSpot account.