---
title: "CRM Views: Auto-Save and Collaborative Sharing"
url: https://www.sidekickstrategies.com/hubspot-updates/hubspot-crm-views-auto-save-collaborative-sharing
description: "HubSpot CRM Views now auto-save and include a three-role sharing system. Learn what shipped, how to set it up, and which teams will benefit most."
type: article
updated: 2026-11-16T23:19:05Z
canonical: https://www.sidekickstrategies.com/hubspot-updates/hubspot-crm-views-auto-save-collaborative-sharing
---

# CRM Views: Auto-Save and Collaborative Sharing

> **Tip**
>
> TL;DR: HubSpot CRM Views now auto-save your filter, sort, and column changes across sessions and ship with a three-role sharing system (Owner, Collaborator, Member) so teams can work on shared views without overwriting each other. Available to everyone on all hubs and tiers as a public beta.

## What This Update Actually Is

HubSpot shipped two changes to CRM index pages in one update: reliable auto-save and a structured sharing model. Both affect every object type, including Contacts, Companies, Deals, Tickets, and custom objects.

Auto-save means changes you make to filters, columns, sorting, and visualization settings in a view stick to your profile across browser sessions. No more re-building the same filter every Monday morning.

The sharing model introduces three distinct roles. Each role works inside a layered architecture: every user gets a personal working layer on top of the shared base layer. Changes in your working layer are yours alone until an Owner decides to publish them down to the base layer.

The three roles are:

- **Owner**: full control. Can publish working layer changes to the base layer, manage sharing settings, and assign roles to other humans.
- **Collaborator**: can customize filters, sorting, columns, and visualization settings in their own working layer without touching anyone else's view.
- **Member**: a focused read-access role. Can adjust limited settings like sort order but can't change filters or columns.

Every new or cloned view starts as private and owned by its creator. Sharing is opt-in. Each view supports one primary visualization type, Board, Gantt, Calendar, or Report, with Table always available alongside it.

## Why HubSpot Shipped This

If you've spent any real time in HubSpot portals, you already know the frustration. You set up a Deals view with the exact filters your team needs, leave the page, come back, and it's gone. Or someone else on the team adjusted the shared view and now your columns are scrambled.

We've seen this pattern across hundreds of portals. Accounts end up with 30, 40, sometimes 60 saved views, most of them duplicates or stale experiments nobody remembers creating. The root cause is always the same: the saving behavior wasn't trustworthy, so humans kept making new views instead of maintaining shared ones.

Without role-based controls, any shared view was fragile. One well-meaning rep could reorganize columns for the whole team. This update fixes both problems at the architecture level, not with a workaround.

## How to Use It Step by Step

1. **Navigate to any CRM index page** (Contacts, Companies, Deals, Tickets, or a custom object). The auto-save behavior is on by default for all beta participants. No toggle needed.
2. **Make your changes**: adjust filters, sort order, columns, or switch the primary visualization. HubSpot saves these to your personal working layer immediately.
3. **Create a new view or clone an existing one**. The new view will be private by default. Only you can see it until you share it.
4. **Open the sharing settings** from the view options menu. Add teammates by name or team. Assign each human the Owner, Collaborator, or Member role based on what they need to do.
5. **Let Collaborators and Members work in their personal working layers**. Their changes won't affect anyone else's view.
6. **As the Owner, review your working layer changes and publish to the base layer** when they're ready. All humans on that view will receive the updated base layer.

One important note for beta participants: if you opt out of this feature, changes made while enrolled may not carry over and will be lost. Don't opt out mid-use if your views matter.

## What It Touches in Your HubSpot Strategy

This update lands squarely in the Smart CRM layer, which means it ripples into every hub that surfaces CRM index pages. Sales teams using Deal pipelines, service teams working Ticket queues, and ops humans managing Contact databases all feel this change.

The personal working layer concept is worth understanding deeply. It means your filtered view of a pipeline is now truly yours. You can sort by close date, add a custom column, and switch to Board view, and none of that touches the base layer your manager built.

> **Key takeaway:** The personal working layer separates individual customization from team-wide standards. Owners control what the whole team sees; Collaborators and Members control only what they see. This is the key architectural shift.

For RevOps leaders, this changes how you should think about view governance. Instead of trying to lock views down or delete duplicates reactively, you can now build a small set of intentional shared views, assign the right roles, and let the system enforce the structure.

This pairs naturally with dashboard discipline. If you're already building standardized reporting, check out [reusable metrics on HubSpot dashboards](https://www.sidekickstrategies.com/hubspot-updates/hubspot-reusable-metrics-dashboards) for the same kind of structured, shareable visibility across your team.

On the data side, the visualization options (Board, Gantt, Calendar, Report) mean this isn't just a list-management feature. Sales leaders can build a Gantt view of deals by expected close date, share it with the team at the Member level, and publish updates without any rep accidentally rearranging it.

> **Key takeaway:** View governance is now a RevOps responsibility. Build a naming convention for shared views, document who owns each one, and audit your existing views before assigning roles. The clean slate opportunity is real.

If your team is also working through a broader portal setup or onboarding, the [HubSpot implementation checklist](https://www.sidekickstrategies.com/blog/hubspot-implementation-checklist) covers the process-mapping and data-structure steps that make view governance decisions like this one land correctly.

## Who Should Care Most

This update matters most to three types of humans:

- **RevOps and CRM admins**: now have a real tool for view governance. Assign ownership, clean up duplicates, and set standards without relying on team discipline alone.
- **Sales managers**: can build a canonical pipeline view, share it at the Member level for reps, and publish updates without fear of a rep reorganizing the whole thing.
- **Service and support team leads**: benefit from stable Ticket queue views. Assign triage filters to a base layer, let agents work in their personal layers, and publish changes when queue priorities shift.

If your company has more than five humans touching a CRM index page regularly, this update is worth setting up intentionally, not just leaving to default behavior.

## George's Take

> CRM views have always been where the rubber meets the road. The data model can be perfect, the automations can be elegant, but if the humans doing the daily work can't trust that their view will look the same tomorrow, none of it matters. Auto-save sounds small. It isn't.
>
> _George B. Thomas_

What excites me most here isn't the auto-save, honestly. It's the layered architecture. The idea that every human gets a personal working layer on top of a shared base layer is how collaborative tools should work. It respects individual workflow preferences without letting individual preferences break the team's shared reality. I've watched RevOps leaders spend real hours every quarter cleaning up view chaos. This update makes that a one-time project, not a recurring chore. Set it up right once, assign roles intentionally, and your CRM index pages can flourish as the actual daily home base for your team.

If you want help auditing your current views, assigning the right roles, or building a governance model that scales as your team grows, that's exactly the kind of work we do in a Sidekick strategy session. Book a call and let's make your portal work the way it should.

## Frequently Asked Questions

### Does HubSpot CRM Views auto-save work for all object types?

Yes. Auto-save applies to all CRM index pages including Contacts, Companies, Deals, Tickets, and custom objects. Changes to filters, columns, sorting, and visualization settings are saved to your personal profile and persist across browser sessions without any extra steps.

### What is the difference between a Collaborator and a Member in HubSpot CRM Views?

A Collaborator can customize filters, sorting, columns, and visualization settings in their personal working layer. A Member has a more restricted role and can only adjust limited settings like sort order. Neither role can publish changes to the shared base layer. Only the Owner can publish to the base layer.

### Will my CRM view changes affect my teammates' views?

No. Every user works in a personal working layer that sits on top of the shared base layer. Your changes only affect your own view. The base layer, which all teammates see by default, only changes when the view Owner publishes an update from their working layer to the base layer.

### What happens to my CRM views if I opt out of the auto-save beta?

HubSpot warns that if you opt out of this feature, any changes made while you were enrolled in the beta may not carry over and will be lost. Don't opt out if you've been actively customizing views during the beta period without first documenting your setup.

### Which HubSpot hubs and tiers get CRM Views auto-save and collaborative sharing?

This feature is available on all hubs and all tiers, including Free, Starter, Professional, and Enterprise. It's currently in public beta, meaning everyone in your account is automatically enrolled. No manual opt-in is required.

### How should a RevOps team prepare before assigning roles in CRM Views?

Start by auditing your existing views and removing duplicates or stale ones. Then identify one Owner per shared view, typically a team lead or RevOps admin. Document a naming convention for views before sharing them widely. Assign Members and Collaborators only after the base layer reflects your actual team standards.

## Key facts

- **Format:** HubSpot Update
- **Published:** November 16, 2026

---
Source: https://www.sidekickstrategies.com/hubspot-updates/hubspot-crm-views-auto-save-collaborative-sharing
Sidekick Strategies · HubSpot consulting and content operations
