The “CRM for Everyone” rollout that landed in Q1 2026 is not a skin. It changes how non-sales teams (legal, finance, ops) hold work inside CRM without holding seats they shouldn’t.
The Core Idea: Team Modules
Team Modules are scoped containers a downstream team owns end-to-end — separate from your sales pipeline but able to receive Requests from it. Think of them as lightweight Desk-style queues built natively in CRM, with their own layouts, statuses, and SLAs.
Deals (sales) → Request → Legal Review (team module) → Status: Approved → fires back to DealThe win: legal stops living in spreadsheets, and you don’t pay full CRM seats to give them a tab.
What to Migrate First
If you’re on a pre-2026 setup, start with the workflows you already hacked together:
- Custom modules used as approval queues (move them to Team Modules).
- Email-based handoffs to ops (replace with Request fields on the parent module).
- Shared inboxes mirrored as tasks (consolidate into a single team queue).
Don’t migrate modules that have heavy reporting dependencies yet — Analytics joins on Team Modules are still being stabilized.
Permission Model Has New Levers
The classic Profile + Role + Data Sharing trio now has a fourth dimension: Team Membership. A user can hold a CRM Standard license but be a full owner inside a Team Module without seeing Deals at all. Audit your existing “View All” profiles before turning this on — they will leak.
Operational Tabs vs Standard Tabs
Operational tabs (the new request-driven UI strip) render conditionally based on record state. Use them for “what should this user do next on this record” not for navigation. If you start using them as menus you’ll regret it within a quarter.
What to Do This Week
- List every custom module currently used by a non-sales team.
- Pick the lowest-risk one and prototype it as a Team Module.
- Run a permission audit on profiles with global view rights.
- Don’t touch Operational Tabs until you’ve nailed Team Modules.
