Definition
Analytics Groups is a Setup feature that controls user access to CRM Analytics (formerly Tableau CRM) applications, dashboards, and datasets. Administrators create groups and assign users to them, then grant each group specific permissions such as viewing, editing, or managing analytics assets.
Real-World Example
At Summit Financial, the admin creates an Analytics Group called "Regional Managers" and assigns all eight regional sales managers to it. The group is given Viewer access to the executive sales dashboard and Editor access to the regional performance lens. This ensures managers can customize their own regional views without modifying the executive-level analytics.
Why Analytics Groups Matters
Analytics Groups solve a critical governance problem in CRM Analytics by enabling role-based access control without requiring individual user configuration. Rather than granting permissions to each analytics asset separately for every user, administrators assign users to groups once, then apply permissions at the group level to dashboards, lenses, and datasets. This approach scales dramatically in larger organizations where manually managing hundreds of individual user permissions would be error-prone and time-consuming. Analytics Groups specifically bridge the gap between Salesforce's identity management and analytics-specific access needs, ensuring that users see only the analytics content relevant to their role.
As organizations scale beyond 50-100 analytics users, the absence of proper Analytics Groups structure creates significant pain points. Without groups, admins face permission sprawl where individual user access becomes undocumented and difficult to audit, leading to either overly permissive access (security risk) or constant permission requests creating bottlenecks. When a manager is promoted or transfers to another department, updating permissions across dozens of analytics assets individually is error-prone. Additionally, without groups, organizations struggle to maintain consistent analytics experiences—different users with the same job function may have different access levels simply due to oversight. The real-world consequence is either restricted analytics adoption (users can't access what they need) or compliance violations (users have access to sensitive financial or customer data they shouldn't see).
How Organizations Use Analytics Groups
- Glacier Insurance Group — Glacier created five Analytics Groups aligned to their claims organization: Adjusters, Supervisors, Regional Managers, Finance, and Executives. Adjusters received Viewer-only access to claim processing dashboards but not cost analytics. Supervisors were given Editor permissions to customize views by adjuster performance. This granular group structure reduced their analytics support tickets by 60% and ensured that cost data remained confidential—Finance could see profitability lenses that no other group could access, protecting competitive pricing information.
- Meridian Tech Solutions — Meridian uses Analytics Groups to manage access across their customer success and sales organizations with distinct analytical needs. They created a 'Customer Success Managers' group with Editor access to health score lenses and renewal risk datasets, while their 'Sales Development' group got Viewer access only to pipeline summary analytics. When they onboarded new customers, they simply assigned the customer success manager for that account to the appropriate group rather than individually configuring dozens of dashboard permissions, reducing onboarding time from 4 hours to 15 minutes.
- Heritage Manufacturing — Heritage leverages Analytics Groups hierarchically by creating 'Plant Operations' and 'Corporate Operations' groups with different access levels to production quality datasets. Their advanced approach includes nested functionality: corporate executives are in both the corporate and read-only plant operations groups, allowing them to see both strategic rollups and granular plant-level details. This multi-group membership approach lets them create tiered analytics access without duplicating datasets or lenses, and they use it to support their matrix organizational structure where many people have dual reporting lines.