Customization | Entry 15
Yes. HubSpot’s customizable middle column can bring record-specific summaries, reports, associated information, external data, and useful actions into the record staff already use. The exact experience may rely on standard HubSpot cards, an installed app, or custom development.
The phrase custom center feed is sometimes used informally for the large middle column of a HubSpot CRM record. It is the central workspace staff see when they open a contact, company, donation, household, volunteer assignment, program enrollment, membership, sponsorship, or another supported record.
Administrators can organize supported cards into tabs, sections, and side-by-side layouts. Depending on the nonprofit’s configuration, those cards can present properties, associated records, activity summaries, reports, historical trends, pipeline progress, important dates, data-quality information, app-supplied insights, and record-specific actions.
A CRM record should help staff understand a relationship, not simply store fields. Useful information is often scattered across donations, sponsorships, activities, reports, associated records, and external systems. A carefully designed middle column brings the most relevant context into one working experience.
Property lists, data highlights, association tables, activity totals, report cards, stage and date trackers, property history, and quick actions can solve many needs without custom development.
When standard cards are not enough, a supported app card or custom UI extension can combine sources, apply specialized calculations, guide a workflow, retrieve external data, or provide approved actions.
Use the simplest option that answers the staff member’s question reliably. Custom development adds flexibility, but it also brings technical design, authentication, testing, security review, maintenance, and support responsibilities.
A corporation’s record is associated with annual sponsorships, corporate donations, employee volunteers, partnership contacts, sponsor benefits, and stewardship activities. A Sponsorship Overview card could turn those records into a useful relationship summary.
Some of this may be achievable through HubSpot properties and record-level report cards. A highly tailored scorecard with custom calculations, visual treatments, or actions may require an app card or UI extension.
A Volunteer Engagement card could summarize lifetime hours, hours served this year, completed assignments, programs supported, training, expiring certifications, upcoming shifts, absences, and the assigned coordinator.
| Volunteer activity | Hours |
|---|---|
| Food distribution | 48 |
| Event support | 22 |
| Mentoring | 36 |
| Administrative support | 14 |
| Total | 120 |
This summary only works when volunteer assignments, attendance, service dates, approved hours, and associations are structured consistently. A card cannot reliably summarize information stored only in notes or disconnected spreadsheets.
HubSpot report cards can place a report in the context of the current record. Depending on the report and configuration, the card may show data for the subject record, data from associated records, or broader unfiltered data for comparison.
Comparison groups must be defined carefully. A precise-looking benchmark is not useful if “similar donors” combines people with unrelated giving levels, interests, locations, acquisition sources, or relationship histories.
A supported app card may retrieve relevant information from fundraising, volunteer, learning, grants, case-management, accounting, membership, advocacy, or impact platforms. The data can sometimes be synchronized into HubSpot beforehand or retrieved from its source when staff need it.
The data may become available to properties, lists, reports, and workflows, but it requires synchronization, conflict, storage, freshness, and permission rules.
The data may remain in its source system, but the experience depends on secure authentication, system availability, performance, and supported real-time access.
The choice should reflect how staff need to use the information, not merely where it can be displayed.
HubSpot can support custom app experiences and external-system interactions on CRM records, but the implementation must follow its supported app-card, UI-extension, authentication, component, domain, and security requirements. Browser policies and the external site’s own framing restrictions also apply.
The feasibility of a specific embedded or external experience should be confirmed during technical discovery.
A custom card is the presentation layer. It does not fix missing records, inconsistent amounts or dates, unreliable associations, unclear calculation rules, duplicates, poor synchronization, or incomplete historical data.
The complete solution may involve properties, rollups, custom objects, associations, workflows, reports, custom code, APIs, an app, data synchronization, and governance. The card is what staff see, but every layer behind it determines whether they can trust the answer.
Review who can see the card, which records and properties they can access, whether external information is transmitted or cached, how each request is authenticated, which actions users may perform, and what happens when access is revoked or a connected system fails.
HubSpot and the source system must independently enforce appropriate authorization. A custom card should not reveal data a user is otherwise prohibited from accessing.
A powerful card can still fail if staff do not understand it or cannot act on it. Define the question it answers, who needs that answer, where it should appear, which data and calculations it uses, how current the information must be, and what the user should do next.
The exact experience depends on the HubSpot subscription, object, record layout, card type, reporting tools, custom-object setup, associations, permissions, team views, conditional display rules, installed apps, external systems, APIs, authentication, security requirements, data quality, and ongoing maintenance capacity.
Before building, confirm whether a standard card already solves the need, whether a report can be filtered correctly for the current record, whether the underlying associations and data are reliable, whether custom development is necessary, whether any external interaction is supported, and who will own ongoing support.
HubSpot’s available card types, limits, subscriptions, developer components, and external-content rules continue to evolve. Confirm the current record-customization documentation during implementation.