Walk me through the collaboration features available on a CRM Analytics dashboard.

At the dashboard level there's Share — granting access, posting to a Chatter feed, copying a URL that encodes the current view, downloading an image, and Print, which re-lays the dashboard out for PDF. At the widget level there's Set Notification for threshold alerts, Annotate for Chatter discussion with screenshots and @mentions, Share for image, Excel, and CSV downloads, Explore for self-service analysis, and subscriptions for scheduled emails. On top of that there are saved views, the watchlist, and onboarding videos surfaced through a Learn action. None of it costs extra — it all ships with the license.

Why do you tell end users to set their own notifications rather than configuring them centrally?

Because a notification captures the filter context of the dashboard at the moment it's created. A West-region manager who filters to West and sets an alert on 'pipeline below 2M' is watching West's pipeline. An East manager doing the same on the same widget is watching East's. They're personal by design, so a designer setting them centrally would just be broadcasting their own slice of the data. The designer's job is to demo the feature and tell users to filter first, then set the alert.

What limits should users know about with notifications?

Each user is capped at 10 notifications across CRM Analytics, so they should spend them on metrics they genuinely need pushed to them rather than on every tile. There's also the repeat behaviour — the 'notify me only the first time the conditions are met' option. Without it, a metric that sits below target for weeks generates an email on every scheduled evaluation, and people stop reading them. Worth mentioning too that notifications reach the mobile app, which for field teams is often the only touchpoint that lands.

A user complains their export only returned a few rows. How do you diagnose it?

First, what did they export from? A download returns the widget's query result, not the dataset. Exporting a chart grouped by stage gives one row per stage because that's what the query returned — there's no hidden detail underneath. Second, if it was a values table and they got exactly 100 rows, that's the default row limit on the table's query, not a bug. The fix for the first case is to give them a values table with the columns they need; for the second, raise the query limit deliberately.

How high can you raise the export limit, and what would you actually recommend?

10,000 rows is the supported ceiling for a values table. You can technically set it higher, but past that the constraint is the browser rendering and holding the result set client-side, so it becomes slow and unreliable. My recommendation is not to raise the limit on the main dashboard at all — that penalises every user, every load, for one person's occasional export. Instead build a separate download-only dashboard or lens: one values table, the needed columns, a filter panel, and the higher limit. Link to it from the main dashboard so the main one stays fast.

How do you control who can export data out of CRM Analytics?

Downloading is governed by a permission on the user's permission set, so it's controlled centrally rather than per dashboard. If a user says the download option is missing, that's the first thing to check. In organisations where data leaving the platform is a compliance concern, the right lever is simply not granting the permission — trying to design exports out of individual dashboards is both fragile and easy to work around.

What is the Explore action, and when would you disable it?

Explore opens a widget's query — with the current filters applied — in a lens, where the user can change the grouping, measure, or chart type and save the result as their own lens. It's the feature that stops the endless queue of 'can you add a version broken down by product?' requests. I'd disable it on curated executive dashboards where the framing matters, or on embedded and mobile surfaces where dropping into a lens is jarring. To do that I'd uncheck 'show explore actions' on the widget rather than 'show widget actions', because the latter kills the whole menu including sharing, notifications, and annotations.

Explain views and what happens when you share one.

A view is a named set of saved selections and filters on an existing dashboard — not a copy of the dashboard, just a bookmark into a state. You can mark one as your default so the dashboard opens on your slice. When you share the dashboard URL while on a view, the link encodes the view ID, so the recipient lands on the same filters. Two caveats: they still need access to the dashboard, and row-level security applies to them, so identical view URLs can legitimately show two people different totals.

Compare widget subscriptions and table subscriptions.

Widget subscriptions email you rendered widget images on a schedule — daily, weekly, monthly — and you can add widgets from several different dashboards into one subscription, so it becomes a personal digest rather than a per-dashboard feature. The widgets in the email are clickable and deep-link back into the org. Table subscriptions are different: they require a separate permission, 'Subscribe to CRM Analytics tables', and they deliver an actual CSV attachment rather than images, subject to roughly a 3MB file-size limit. That makes them a scheduled, security-respecting data extract with no integration work — extremely valuable for finance and operations teams.

What is the watchlist and how does it differ from a notification or subscription?

The watchlist pins a metric to your CRM Analytics home screen, trending over time, with an influence direction telling it whether up is good or bad and a reference line for a target or threshold. The three are complementary: a notification is event-driven and only speaks when a condition is met, a subscription is schedule-driven and arrives regardless, and the watchlist is glance-driven — always on the page you land on. Together they mean a user encounters your data without deliberately opening a dashboard.

How do you attach help content to a widget, and what's the common mistake?

You set the widget's onboarding property to a video URL, which gives end users a Learn action in the widget menu. The gotcha is that the URL must be the YouTube embed link from Share → Embed, not the normal watch link from the address bar. Pasting a watch link fails silently — the property saves, the Learn action appears, and the panel just opens to nothing. So always test the action as a viewer after saving. Content-wise I'd cover the metric definition and source, refresh frequency, how to read the visual, and the one thing people commonly misread.

You've launched a dashboard and adoption is low. What do you do?

I'd assume it's a communication problem before a design problem. Concretely: announce it in the relevant Chatter group with context rather than emailing a bare link; run a short session showing users how to save a default view of their own slice, set a subscription for their Monday meeting, pin a couple of watchlist metrics, and set a notification on the one number they'd want to be told about; attach onboarding videos to the two or three widgets with non-obvious business rules; and make sure a values table exists for the people who will export regardless. Every one of those is already in the license — the gap is almost always that nobody told the audience the buttons exist.

Sponsor this projectKeep the curriculum free and open.

Collaboration: Interview Questions

Rehearse common CRM Analytics collaboration interview questions — sharing and views, notifications vs subscriptions, export limits, self-service explore, table subscriptions, watchlists, and how you drive dashboard adoption.

Collaboration: Interview Questions

You've reached the end of the Collaboration section — nice work. Use this page as a study sheet and rehearse each answer out loud.

These are the questions a CRM Analytics candidate genuinely gets asked about the delivery side of the job: how sharing and views behave with security, why notifications belong to the end user, what the export limits really are and how you work around them responsibly, the difference between widget and table subscriptions, and — the one that separates a builder from a consultant — how you actually drive adoption after a dashboard ships.

Try to answer each one in your own words before reading the model answer. That active recall is what makes it stick under interview pressure.

Answer each question aloud first, then compare with the model answer. Pay particular attention to the two that come up most: why notifications inherit the user's filter context, and why you build a separate download dashboard instead of raising the row limit. Both signal real project experience.

When you're ready, head back to the Graded Quiz to prove it — you need 85% to pass, and your score is tracked in your profile.

Interview questions

12 common questions with model answers — rehearse each one aloud.

1
Walk me through the collaboration features available on a CRM Analytics dashboard.
A
At the dashboard level there's Share — granting access, posting to a Chatter feed, copying a URL that encodes the current view, downloading an image, and Print, which re-lays the dashboard out for PDF. At the widget level there's Set Notification for threshold alerts, Annotate for Chatter discussion with screenshots and @mentions, Share for image, Excel, and CSV downloads, Explore for self-service analysis, and subscriptions for scheduled emails. On top of that there are saved views, the watchlist, and onboarding videos surfaced through a Learn action. None of it costs extra — it all ships with the license.
2
Why do you tell end users to set their own notifications rather than configuring them centrally?
A
Because a notification captures the filter context of the dashboard at the moment it's created. A West-region manager who filters to West and sets an alert on 'pipeline below 2M' is watching West's pipeline. An East manager doing the same on the same widget is watching East's. They're personal by design, so a designer setting them centrally would just be broadcasting their own slice of the data. The designer's job is to demo the feature and tell users to filter first, then set the alert.
3
What limits should users know about with notifications?
A
Each user is capped at 10 notifications across CRM Analytics, so they should spend them on metrics they genuinely need pushed to them rather than on every tile. There's also the repeat behaviour — the 'notify me only the first time the conditions are met' option. Without it, a metric that sits below target for weeks generates an email on every scheduled evaluation, and people stop reading them. Worth mentioning too that notifications reach the mobile app, which for field teams is often the only touchpoint that lands.
4
A user complains their export only returned a few rows. How do you diagnose it?
A
First, what did they export from? A download returns the widget's query result, not the dataset. Exporting a chart grouped by stage gives one row per stage because that's what the query returned — there's no hidden detail underneath. Second, if it was a values table and they got exactly 100 rows, that's the default row limit on the table's query, not a bug. The fix for the first case is to give them a values table with the columns they need; for the second, raise the query limit deliberately.
5
How high can you raise the export limit, and what would you actually recommend?
A
10,000 rows is the supported ceiling for a values table. You can technically set it higher, but past that the constraint is the browser rendering and holding the result set client-side, so it becomes slow and unreliable. My recommendation is not to raise the limit on the main dashboard at all — that penalises every user, every load, for one person's occasional export. Instead build a separate download-only dashboard or lens: one values table, the needed columns, a filter panel, and the higher limit. Link to it from the main dashboard so the main one stays fast.
6
How do you control who can export data out of CRM Analytics?
A
Downloading is governed by a permission on the user's permission set, so it's controlled centrally rather than per dashboard. If a user says the download option is missing, that's the first thing to check. In organisations where data leaving the platform is a compliance concern, the right lever is simply not granting the permission — trying to design exports out of individual dashboards is both fragile and easy to work around.
7
What is the Explore action, and when would you disable it?
A
Explore opens a widget's query — with the current filters applied — in a lens, where the user can change the grouping, measure, or chart type and save the result as their own lens. It's the feature that stops the endless queue of 'can you add a version broken down by product?' requests. I'd disable it on curated executive dashboards where the framing matters, or on embedded and mobile surfaces where dropping into a lens is jarring. To do that I'd uncheck 'show explore actions' on the widget rather than 'show widget actions', because the latter kills the whole menu including sharing, notifications, and annotations.
8
Explain views and what happens when you share one.
A
A view is a named set of saved selections and filters on an existing dashboard — not a copy of the dashboard, just a bookmark into a state. You can mark one as your default so the dashboard opens on your slice. When you share the dashboard URL while on a view, the link encodes the view ID, so the recipient lands on the same filters. Two caveats: they still need access to the dashboard, and row-level security applies to them, so identical view URLs can legitimately show two people different totals.
9
Compare widget subscriptions and table subscriptions.
A
Widget subscriptions email you rendered widget images on a schedule — daily, weekly, monthly — and you can add widgets from several different dashboards into one subscription, so it becomes a personal digest rather than a per-dashboard feature. The widgets in the email are clickable and deep-link back into the org. Table subscriptions are different: they require a separate permission, 'Subscribe to CRM Analytics tables', and they deliver an actual CSV attachment rather than images, subject to roughly a 3MB file-size limit. That makes them a scheduled, security-respecting data extract with no integration work — extremely valuable for finance and operations teams.
10
What is the watchlist and how does it differ from a notification or subscription?
A
The watchlist pins a metric to your CRM Analytics home screen, trending over time, with an influence direction telling it whether up is good or bad and a reference line for a target or threshold. The three are complementary: a notification is event-driven and only speaks when a condition is met, a subscription is schedule-driven and arrives regardless, and the watchlist is glance-driven — always on the page you land on. Together they mean a user encounters your data without deliberately opening a dashboard.
11
How do you attach help content to a widget, and what's the common mistake?
A
You set the widget's onboarding property to a video URL, which gives end users a Learn action in the widget menu. The gotcha is that the URL must be the YouTube embed link from Share → Embed, not the normal watch link from the address bar. Pasting a watch link fails silently — the property saves, the Learn action appears, and the panel just opens to nothing. So always test the action as a viewer after saving. Content-wise I'd cover the metric definition and source, refresh frequency, how to read the visual, and the one thing people commonly misread.
12
You've launched a dashboard and adoption is low. What do you do?
A
I'd assume it's a communication problem before a design problem. Concretely: announce it in the relevant Chatter group with context rather than emailing a bare link; run a short session showing users how to save a default view of their own slice, set a subscription for their Monday meeting, pin a couple of watchlist metrics, and set a notification on the one number they'd want to be told about; attach onboarding videos to the two or three widgets with non-obvious business rules; and make sure a values table exists for the people who will export regardless. Every one of those is already in the license — the gap is almost always that nobody told the audience the buttons exist.

Discussion

No comments yet — be the first to start the discussion.

Why Collaboration Matters

The collaboration features shipped with your CRM Analytics license — sharing, notifications, annotations, downloads, explore, views, subscriptions, and watchlists — and why telling users they exist is the single biggest driver of dashboard adoption.

Sharing a Dashboard

Use the dashboard-level Share action in CRM Analytics — grant access, post to the Chatter feed, copy a URL that encodes your current view, download the dashboard as an image, and print a PDF-friendly layout.