Skip to content
Tutorials Center
My learning

Topics

Lesson 27 of 36 ยท Reports and Dashboards

Sharing Folders, Subscriptions and Report Limits

Organize and govern Salesforce analytics: folder sharing levels, who can see which report, subscriptions, report snapshots, report limits and a clean-up routine, with JavaScript stand-ins.

A Salesforce org that has been used for a few years usually holds thousands of reports and hundreds of dashboards: many are copies, many are abandoned, and a few are important but nobody remembers who owns them. Good administrators treat analytics like a library with rules: a clear folder structure, sensible sharing, scheduled delivery for the reports that matter, and regular clean-up. This lesson covers the governance side of reporting. The Salesforce screens are described in words; the demonstrations are labelled JavaScript stand-ins, not Salesforce.

Folders and sharing

Every report and dashboard lives in a folder. A folder has three access levels that you assign to users, roles, roles with subordinates, public groups or (with the right setup) the whole org:

Access What the person can do
Viewer Run reports and open dashboards in the folder
Editor Viewer, plus edit, move and delete items, and add new ones
Manager Editor, plus rename the folder and change who it is shared with

Everything in a folder shares the folder's access. There are two special places: My Private Reports / Dashboards (only the author sees them) and Public Reports / Dashboards (a legacy shared folder; do not use it for new work). Create folders by team and purpose, for example Sales Leadership, Support Operations and Admin Tools, and share each with the right group rather than "all internal users".

Note the difference between folder access and record access:

  • Folder access decides who can open the report.
  • Record sharing (OWD, roles, sharing rules) decides which rows a report shows to its viewer.

So a user with Viewer access to a folder still sees only the records they are allowed to see. The exception is the dashboard running user, discussed in Dashboards and components.

Permissions that matter for reporting

Users need permissions to build reports, not just to open them. The main system permissions (granted through a profile or permission set) are:

  • Run Reports to open reports.
  • Create and Customize Reports and Report Builder to create reports with the builder.
  • Create and Customize Dashboards and Manage Dashboards in Public Folders.
  • Schedule Reports, Subscribe to Reports, Export Reports.
  • Manage Reports in Public Folders and View Reports in Public Folders for admin-style control.
  • View All Data and Modify All Data override all sharing: give them rarely.
  • Edit My Reports and Edit My Dashboards control editing of private items.

The ability to export reports deserves attention: it is how data leaves Salesforce. Consider turning off Export Reports for roles that do not need it.

Subscriptions and scheduled runs

A user can subscribe to a report (Lightning: the Subscribe button, choose frequency, time and, optionally, a condition such as "send only if the record count is greater than 0"). The report runs as the subscriber at the chosen time and emails a summary, with a link. Admins can set subscriptions for other people or groups (if allowed) and the number of subscriptions per person is limited by edition (typical values are five for some editions and more for Enterprise and Unlimited; check your org's limits in Help).

You can also schedule a dashboard refresh (not available for dynamic dashboards) so that data is ready when people arrive. The refreshing and emailing run in the background and they share the daily budget of scheduled jobs.

Reporting snapshots

A reporting snapshot (Setup, then Reporting Snapshots) saves the results of a tabular or summary report into a custom object on a schedule. That builds history: "how many open opportunities did we have on the first of each month?" A normal report only shows the present, but with a snapshot you get a record of the past that you can report on and chart. You need a source report, a target custom object with the right fields, and a mapping between them. Snapshots run on a schedule and count against the org's limits.

Limits to know

Numbers vary by edition and release, so verify in the Salesforce Help limits pages, but these are the ones that matter in daily work:

  • The report run page shows up to 2,000 rows; summary and matrix reports show totals for all matching rows.
  • A report can include up to 100 columns in a regular format.
  • Reports time out if they run for too long (long, unselective reports on huge objects). Add filters or use a more selective report type.
  • Dashboards hold up to 20 components and three filters.
  • A user can have a limited number of dashboard refreshes per hour (manual refresh) and scheduled ones.
  • Joined reports have their own block and filter limits.
  • Exports from the report page are limited in size; for millions of rows use the Data Loader or Bulk API (see Importing data and the Data Loader).

A clean-up routine

Run this every quarter, with a note of the results:

  1. Make a report of reports: the Reports and Dashboards report types (Administrative Reports) show Last Run Date, Created By, Folder and Number of Runs.
  2. Find items not run in 12 months and notify the owners; archive them (move to an "Archive - to delete" folder with Manager-only access).
  3. Delete the archived items after a further grace period (deleted reports go to the Recycle Bin for 15 days).
  4. Review who has Export Reports, View All Data and Manage Public Reports.
  5. Check the ownership of reports owned by inactive users (reassign them, or they become hard to manage).
  6. Rename obvious duplicates ("Copy of Copy of Pipeline") and document the official ones in the description.
flowchart TD
  A["Report of reports: last run date"] --> B{"Not run in 12 months?"}
  B -->|"Yes"| C["Move to Archive folder; tell owner"]
  B -->|"No"| D["Keep; check name and owner"]
  C --> E{"Anyone objects after 30 days?"}
  E -->|"No"| F["Delete (15 days in Recycle Bin)"]
  E -->|"Yes"| G["Restore to a team folder"]

A simple clean-up workflow.

Stand-in: who can open this report?

This stand-in is not Salesforce. It models folder access by user, role and group, and takes the strongest level.

JS Stand-in: folder access resolution

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Stand-in: finding stale reports

JS Stand-in: clean-up candidates

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. A user has Viewer access to a folder. What determines which rows a report in it shows them?

    Folder access controls opening the report; record sharing controls the rows.
  2. 2. Which folder access level lets someone change who the folder is shared with?

    Only Manager access can change the folder's sharing and name.
  3. 3. What is a reporting snapshot used for?

    Snapshots store results over time so you can report on trends that a live report cannot show.
  4. 4. Why consider removing Export Reports from some roles?

    Controlling export lowers the risk of data leaving the org.

Summary

  • Organize reports and dashboards in folders by team, and share with Viewer, Editor or Manager access to groups and roles.
  • Folder access opens the report; record sharing decides the rows; reporting permissions control building, scheduling and exporting.
  • Subscriptions and scheduled refreshes deliver numbers automatically; reporting snapshots build history.
  • Review analytics every quarter: archive what is unused and check ownership and export rights.

Next: Importing data and the Data Loader