The Design Layer: Lenses, Dashboards & Apps

In the last lesson we shaped raw data into fast, optimized datasets. But a dataset by itself is invisible to business users — it needs a face. That is the job of the design layer, where datasets become things people actually look at and explore: lenses, dashboards, and apps. These three concepts are the everyday vocabulary of CRM Analytics, so let's make them second nature.

Lenses: quick, self-service exploration

A lens is the fastest way to look at a dataset. Open a dataset, and you are dropped into a lens: a lightweight exploration surface where you can group by a field, change the measure, switch chart types, and filter — all in a few clicks.

Think of a lens as asking a single dataset a quick question:

• "How many opportunities do we have by stage?"
• "What is total revenue by region this quarter?"

You are not building anything polished; you are exploring. Lenses are inherently self-service — a curious user can answer their own question without waiting on a developer.

Dashboards: curated, multi-widget analytics

When a set of questions matters enough to answer again and again — for a team, a meeting, a role — you graduate from a lens to a dashboard.

A dashboard is a curated collection of widgets: multiple charts, tables, filters, toggles, number tiles, and text, arranged deliberately on a canvas. Unlike a single lens, a dashboard can:

• Pull from multiple datasets at once.
• Combine several visualizations into one coherent story.
• Offer interactivity — filters and selections that update the whole page together.

A dashboard is designed. Someone decides what questions the audience cares about, picks the right charts, and lays them out so the answer is obvious at a glance. (Good dashboard design is a skill in its own right — we cover it later in the course.)

Apps: grouping and, crucially, sharing

So you have lenses and dashboards. Where do they live, and who is allowed to see them? Enter the app.

An app is essentially a folder that groups related CRM Analytics assets together:

• Dashboards
• Lenses
• Datasets
• Stories

But an app is more than a tidy container. It is also the unit of access and sharing. You do not typically share each dashboard one by one; you share the app, and everything inside inherits that access.

This is why organizations create purpose-built apps by function:

• A Sales app for pipeline and forecast dashboards, shared with the sales team.
• An HR app for headcount and attrition, shared only with HR.
• A Finance app for revenue and margin, restricted to finance.

Apps can be private — visible only to their creator while a dashboard is a work in progress — or shared with specific users, roles, or groups once it is ready. That flexibility lets you build safely in private, then publish to exactly the right audience.

How the three fit together

A clean way to remember the design layer:

1. A lens explores one dataset for a quick answer.
2. A dashboard curates many widgets (across datasets) into a designed, shareable view.
3. An app groups dashboards, lenses, datasets, and stories — and controls who can access them.

Lenses are for thinking, dashboards are for communicating, and apps are for organizing and securing. With the design layer understood, we are ready for the smartest part of the platform: the intelligence layer, where Einstein Discovery turns datasets into predictions.