You rely on HubSpot to surface the insights your team needs to take action fast.
But when your index pages are cluttered with irrelevant data or missing critical deal or contact info, those insights get buried.
Every time a rep scrolls to the right field or re-applies the same filter, you’re losing time that could be spent moving opportunities forward.
Whether you’re leading a sales funnel, managing post-sale support, or running operations behind the scenes, poor index page setup can drain productivity and cloud decision-making.
Reps miss timely follow-ups.
Managers waste cycles piecing together the current pipeline status.
And your reporting can drift off-course if each user sees and filters data differently.
This guide walks you through how to customize index page columns and filters inside HubSpot.
You’ll learn how these settings work, how to configure them based on team needs, which slipups to avoid, and how to measure the time and efficiency gains inside your portal.
Managing Columns and Filters in HubSpot
Every list view in HubSpot, whether for Contacts, Companies, Deals, Tickets, or custom objects, lives on an index page.
This is your team’s daily workspace, where records show up in rows with fields arranged as columns.
Two elements power the data on display:
- Columns: Determine which fields show for each record, such as Deal Name, Close Date, or Lifecycle Stage. These appear without opening individual records.
- Filters: Limit which records populate the list. You can filter by properties like Deal Stage, Owner, Region, or Lifecycle Stage to focus on what matters right now.
You’ll find these controls under pages like Contacts > Contacts or Sales > Deals.
Look for Table actions or Edit columns to customize what displays.
Filter options are located on the left-hand panel of most index pages.
What you see is permission-based.
Super Admins can create shared views and influence team defaults, while standard users may be limited to their personal opinions depending on account permissions.
You can also create and save filtered views for different scenarios.
These Saved Views are reusable and can be kept private or shared with team members to keep everyone working from the same lens.
How It Works Under The Hood
When you open a HubSpot index page, HubSpot pulls live record data and arranges it based on your selected columns, filters, and sorting rules.
Each column maps to a property in your CRM data model.
Each filter defines the criteria that determines which records qualify to show.
Here’s what powers it:
- Inputs:
- Object Type: Contacts, Deals, Companies, Tickets, or a custom object
- Selected Columns: The properties you choose to display inline
- Filter Set: The rules that define which records appear
- Optional Sort Order: How records are prioritized
- Saved View Selection: The stored set of columns, filters, and sort settings
- Outputs:
- A Record Table: A formatted list that updates as record data changes
- Workflow-Friendly Views: Lists aligned to individual or team needs without changing the underlying data
Views do not change underlying data.
They change visibility and context, not the record values.
Admins can also create shared views that teams rely on for consistent daily workflows, training, and reporting alignment.
Additional settings let you:
- Sort by a column to prioritize work
- Pin frequently used views
- Set recommended defaults that support smoother onboarding
Main Uses Inside HubSpot
Separate Pipelines By Team Or Stage
Managing multiple segments or sales funnels often requires distinct views.
Filters help reps cut through noise and focus on the right pipeline.
Example:
A SaaS company has two deal flows, SMB and Enterprise.
The sales manager creates two Saved Views:
- SMB Active Deals, filtered to Pipeline = SMB and Stage is not Closed
- Enterprise Closing Soon, filtered to Pipeline = Enterprise and Close Date within the next 30 days
Each view includes columns like Deal Owner, Amount, and Close Date.
Now each seller focuses on what matters, and the manager reviews both flows quickly.
Identify Priority Contacts For Follow-Up
SDRs waste time rebuilding the same filters every morning.
Shared views create a consistent daily hit list.
Example:
An SDR manager configures a Contacts view with filters:
- Lead Status = New or Attempted To Contact
Columns include Last Contacted, Source, and Company.
Sorting by Last Contacted highlights which leads have been untouched the longest.
Every SDR starts from the same queue without prep.
Monitor Ticket Load For Service Teams
Support teams work faster when they can triage at a glance.
Columns and filters make urgency obvious.
Example:
A Service Manager builds a Ticket view filtered to:
- Status = Open or Waiting On Customer
Columns include Ticket Owner, Time To Close, and Customer Name.
Sorting by Priority helps assign resources without bouncing between dashboards.
Standardize Operational Visibility For RevOps
RevOps needs views that match the conditions used in dashboards, forecasts, and audits.
Shared views reduce misalignment.
Example:
A RevOps lead sets up shared Deal views that mirror forecast dashboard logic.
With standardized columns like Deal Stage and Forecast Category, there is less ambiguity across roles.
Common Setup Errors And Wrong Assumptions
- Point: Changing columns will not change the underlying data
Clarification: You are not editing fields; you are selecting which fields to display. - Point: Private views can hurt team alignment
Clarification: When users work from different setups, consistency breaks down. Shared views simplify training and reduce reporting confusion. - Point: Too many columns create cognitive overload
Clarification: More fields do not equal more clarity. Aim for 6 to 8 columns so users can scan without excessive horizontal scrolling. - Point: Permissions can block the view setup and adoption
Clarification: If users cannot create, edit, or share views, your setup stalls. Confirm roles and permissions under Settings > Users & Teams.
Step-By-Step Setup Or Use Guide
Before you begin, confirm you have appropriate permissions.
Super Admins can create shared views and shape team-wide defaults.
Standard users can typically create and pin their own views, depending on the portal.
- Open The Relevant Index Page: Navigate to Contacts, Companies, Deals, Tickets, or your custom object from the top menu.
- Select Or Create A View: Use the view dropdown to open an existing view, or click Create new view. Choose Private, Shared, or Team visibility based on your needs.
- Add Filters: Use the left Filters panel to define which records should appear. Filter by owner, stage, date, or any other relevant property.
- Edit Columns: Click Table actions or Edit columns. Select the fields to display, then reorder them using drag-and-drop.
- Set Your Sorting: Sort by a key property, such as Close Date, Last Contacted, or Priority, based on your workflow.
- Save And Name the View: Click Save view. Choose a name that clearly explains the use case, and set the visibility level.
- Pin Key Views: Pin the views your team uses daily so they are always visible in the view bar.
- Standardize For Teams: If you manage the portal, document which shared views each team should use and include them in onboarding.
Measuring Results In HubSpot
Customizing views only matters if it helps teams act faster and keep data cleaner.
Here’s what to track:
- Time Per Lookup: Shorter time to find the right records indicates stronger views.
- Field Completeness: Use data quality dashboards to confirm visible properties align with required fields.
- Shared View Adoption: Monitor whether teams actually use the shared views instead of rebuilding private ones.
- Reporting Alignment: Confirm that the view logic matches dashboards, exports, and forecast definitions.
- Pipeline Integrity: Watch for gaps in fields like Deal Stage, Owner, or Close Date. Strong views make incomplete records easier to spot and fix.
Use HubSpot reporting to build simple summaries based on your most important Saved Views and review them regularly with team leads.
Short Example That Ties It Together
Your sales org scales from three to ten reps.
The default Deals table becomes noisy, mixing reps, pipelines, and closed deals.
To fix it:
- A manager creates a Saved View called My Active Deals.
- Filters: Deal Stage is not Closed, and Owner = Me
- Columns: Deal Name, Amount, Deal Stage, Close Date, Forecast Category
- Sorting: Close Date ascending
- The view is pinned for daily use.
Now each rep sees only their active pipeline.
Leadership reviews a consistent slice of the pipeline and trusts that day-to-day execution matches the reporting story.
How INSIDEA Helps
As your CRM matures, maintaining view customization becomes harder.
More teams, more objects, and more reporting dependencies require ongoing alignment between data structure and daily workflows.
INSIDEA helps you design, implement, and maintain index views that support real execution, not just cosmetic organization.
Here’s how we support your team:
- HubSpot onboarding with clean data models and consistent views
- View optimization across sales, marketing, and service objects
- Workflow and automation support aligned to your index view strategy
- Reporting setup using standardized filters for accuracy
- Team training so adoption sticks and private view sprawl stays under control
- Ongoing data hygiene to prevent view decay over time
If you want to hire HubSpot experts to standardize views across teams, INSIDEA can help you implement a clean, scalable approach.
If you need HubSpot consulting services to keep your CRM aligned as your processes evolve, our team can support the strategy and maintenance.
Visit INSIDEA to get started.
Well-structured views are not just easier to use; they are operational leverage.
When everyone sees the correct data at the right time, action happens faster.
