Skip to main content

Report Sender v3.20 - April 2026

New settings page and user walkthrough

Updated today

This month, we're continuing to make Report Sender easier to use with a new settings page and a new user walkthrough.

Release Schedule

  1. April 29, 2026 - Available on the AppExchange

  2. April 29, 2026 - Pushed to Sandboxes

  3. May 11, 2026 - Pushed to Production orgs

Release Notes

Settings Page

Previously, to change custom settings, you had to use the Salesforce setup, which meant many people did not know how to access them. To make it easier, we have added a new Report Sender Settings tab. Starting with just two settings, but this page will have more in future releases!

To edit settings, a user must have the CloudAnswers Report Sender Admin permission set.

Log Settings

Logs are used to keep track of which reports or dashboards are sent and when. You can view logs from the Report Sender tab using the drop-down for any schedule. Log settings control how many days until the Report Sender logs are deleted. This is an org-level setting.

Email Domain Restrictions

Plus and Premium customers

If you want to control who reports and dashboards can be sent to, go to Email Domain Restrictions and add domains to the safe list or block list. For example:

  1. Add free email domains such as gmail.com, outlook.com, and yahoo.com to your block list to ensure that recipients are only corporate addresses.

  2. Add your company, customer, or partner domains to the safe list to prevent people from sending reports and dashboards to anyone outside of those companies.

See Report Names for Multiple-File Schedules

For users in our multiple-file beta, which lets you send multiple reports in a single email, you can now see all report names in the list view.

New User Walkthrough

A simple change to help new users get their first schedule set up. Access the tour anytime using the quick tour link on the dashboard.

Minor Improvements

We've also fixed a variety of bugs and made some minor improvements

  1. Fixed the view for companies that let their trial expire or were downgraded to see which schedules use unsupported features.

  2. Added some error handling for content delivery settings that could break secure file sharing.

  3. Fixed some scenarios where people could get around the safe list or block list when editing, even though the schedule still wouldn't send to those recipients.

  4. Added better error handling for OAuth failures when authorizing Report Sender.

  5. Updated how often we send error emails for fatal errors to daily instead of hourly.

  6. Improved error handling when users are missing certain permissions.

Did this answer your question?