Customization | Entry 13
Yes. Eligible HubSpot accounts can create team-specific record views so development, programs, volunteer management, membership, leadership, and other teams see layouts organized around their work. Everyone can use the same underlying record while receiving a different combination of properties, cards, tabs, activities, reports, associations, and actions.
For nonprofits, role-based record views means organizing the CRM experience around a person’s job. HubSpot calls this feature team views. A nonprofit can align HubSpot teams with operational roles such as Development, Programs, Volunteer Management, Membership, or Executive Leadership, then assign a record view to each team.
The view is determined by the user’s assigned main team. It is not automatically selected from a job title, permission set, assigned seat, department property, CRM role, extra-team membership, or a property on the record.
The constituent, donation, household, program, or other record remains the same source of truth for every authorized user.
Each team can receive a different arrangement of properties, tabs, cards, reports, actions, and associated records.
Users who do not receive an applicable team view see the account’s default view for that object.
A single constituent may be a donor, volunteer, member, program participant, event attendee, corporate contact, board member, advocate, and family member. Different teams need different parts of that story to do their jobs well.
Jordan is a recurring donor, active volunteer, parent of a program participant, member, and employee of a corporate sponsor. Every team opens the same contact record, but each team begins with the information most relevant to its responsibilities.
Administrators can design supported team views separately for contacts, companies, deals, tickets, and custom objects. Each layout can prioritize different information across the record page.
Conditional display and team views solve different problems. A team view is based on the user’s main team. Conditional content appears based on properties of the record being viewed.
A team view changes how authorized information is arranged. Removing Lifetime Giving or a Donation association card from a layout does not necessarily prevent a user from finding that information elsewhere.
If information must be protected, configure the appropriate object, record, property, tool, export, communication, and sensitive-data permissions separately.
HubSpot uses the user’s main team for record-view assignment. A person whose main team is Development and extra team is Events receives the Development view. They do not automatically switch between layouts when opening a record.
For staff with hybrid responsibilities, a nonprofit might assign the team reflecting the person’s primary work, create a combined view, improve the default view, allow limited personal customization, use conditional cards, or provide direct access to reports and workspaces for secondary duties.
Too many team views become difficult to maintain, test, document, train, and update. Before creating one, ask whether the team answers meaningfully different questions, maintains different information, and takes different actions. Also decide whether conditional cards, personal customization, a stronger default view, or different permissions would solve the need more cleanly.
The goal is not to create departmental data silos. It is to give different users clearer ways to work with the same connected data.
Team views currently require HubSpot Professional or Enterprise. The available experience also depends on the object configuration, team structure, user permissions, main-team assignments, available cards, installed apps, custom objects, data model, and personal-customization settings.
Before implementation, confirm:
HubSpot’s exact record-layout features and limits can change. Confirm current subscription requirements, supported objects, card and tab limits, team assignment behavior, and personalization controls before implementation.