Customization | Entry 14
Yes. HubSpot can conditionally show or hide certain record cards and custom tabs based on properties of the record being viewed. Donor, volunteer, membership, program, event, and other information can appear only when it applies to that constituent.
HubSpot calls this capability conditional display logic. Administrators set property-based criteria for selected cards and custom middle-column tabs. When a record meets those criteria, the configured content appears. When it does not, that content stays hidden.
The underlying record and its data remain the same. HubSpot changes which parts of the configured layout are visible. It does not create a separate contact, infer a relationship automatically, or change who can access the data.
Based on the staff member’s main HubSpot team. They change the broader layout assigned to Development, Programs, Volunteer Management, or another team.
Based on supported properties of the record being viewed. It shows or hides configured cards and tabs for donors, volunteers, members, participants, and other statuses.
The two can work together. A Development Team view could contain a Major Donor card that appears only when the constituent’s Giving Level meets the nonprofit’s major-gift threshold.
A constituent rarely fits neatly into one category. One person may be a donor, volunteer, member, event attendee, parent, advocate, or several of these at once. Showing every possible section on every contact record creates clutter and makes important information harder to find.
Elena Cruz is a recurring donor, active volunteer, current member, and recent gala attendee. She is not a program participant. Her one contact record can respond to those known relationships.
Because Elena is not an active program participant, the Program Information tab remains hidden. Staff see her actual relationships without creating duplicate contact records.
Cards can present selected properties, associated-record information, activities, reports, pipeline information, app-provided insights, custom-developed content, and quick actions. A custom tab can group several related cards when an entire area of information applies only to certain records.
Conditional warnings can make urgent information easier to notice, but they should not replace workflows, tasks, notifications, or formal compliance procedures when those are also needed.
If Volunteer Status is blank or outdated, the volunteer card may disappear for an active volunteer. If one single-select Constituent Type field forces a person to be either a donor or a volunteer, the layout may miss overlapping relationships.
Nonprofits may need separate status properties, a multiple-checkbox relationship field, workflow-maintained summaries, calculated or rollup properties where supported, or a combination of these approaches. The right structure depends on the organization’s data model and how relationships change over time.
HubSpot evaluates supported properties on the record whose layout is being viewed. If an active volunteer assignment exists only as an associated record, the nonprofit may need a contact property such as Active Volunteer, Current Volunteer Status, or Number of Active Volunteer Assignments.
That summary property may be maintained by a workflow, rollup or calculation, integration, custom-coded process, or manual administration, depending on the subscription and data model.
Hiding a card or tab does not necessarily prevent an authorized user from finding the information through properties, associated records, reports, exports, another record view, or an integrated system.
Review object, record, property, export, tool, integration, and sensitive-data permissions separately whenever information must be protected.
A card should not appear simply because data exists. It should help a staff member answer a question, make a decision, complete a task, avoid an error, understand a relationship, identify a risk, or recognize an opportunity.
HubSpot currently requires a Starter, Professional, or Enterprise subscription for conditional card and tab display logic. Availability also depends on the object, record layout, card type, property configuration, user permissions, team views, installed apps, custom objects, data model, connected systems, and automation capabilities.
Before implementation, confirm which statuses should affect the layout, which properties will control each condition, how those values will be maintained, how overlapping and former relationships will be handled, whether association data must be summarized into properties, what fallback experience blank values receive, and who owns ongoing governance.
HubSpot’s exact criteria, supported cards, tab limits, and subscription requirements can change. Confirm the current record-customization documentation before implementation.
A card should not appear simply because data exists. It should help a staff member answer a question, make a decision, complete a task, avoid an error, understand a relationship, identify a risk, or recognize an opportunity.