Security
You stay in control of your Salesforce org.
Here’s a straightforward rundown of what Pulse can read, what it can create, and what it can’t touch.
It can’t touch your Salesforce records
Pulse can create reports, dashboards, and report formulas. It can’t edit records, fields, users, permissions, flows, or automation.
Your password stays with Salesforce
You connect through Salesforce’s own sign-in screen. Pulse never receives your Salesforce password. An admin installs a metadata-only OAuth registration once for the org; it contains no Apex, objects, fields, or UI.
Your existing permissions still apply
Pulse works with the access of the connected user. If that person can’t see a record or field in Salesforce, Pulse can’t see it either.
It only reads what it needs
Pulse starts with your object names, field names, and available choices. It only queries record data needed to answer the report request.
Shared links don’t expose individual records
A public result can show chart totals and summaries. It doesn’t reveal the Salesforce records behind those numbers.
Your data is used to answer your request
Query results are used to build the report you asked for and show its charts. They aren’t used to make unrelated changes in your org.
It asks for totals, not bulk exports
Most reports need sums, counts, averages, and grouped totals. Pulse limits query results instead of sending full record exports to the reporting model.
Build reports without handing over your Salesforce org.
Create a new report, improve one your team already uses, or build a dashboard. Review the result and publish it directly to Salesforce.
Build a Salesforce report