Salesforce Maps is a managed package add-on. After your org is provisioned with Maps and the package is installed, an admin enables access and builds a first marker layer so reps can see records on the map. These are the broad strokes; follow the current Maps setup guide for exact steps in your release.
- Confirm provisioning and install the package
Make sure your org has the Salesforce Maps add-on, then install the Maps managed package from the link Salesforce provides. Installation adds the Maps app, objects, and tabs to your org.
- Grant access with permission sets
Assign the Maps permission sets and license assignments to the users who need the map. Without the license and permissions, the Maps tab will not appear for a user.
- Build a marker layer
In the Maps app, open the Layers tab and create a marker layer from a report or object. Map the address fields that drive pin placement and pick a render mode such as markers, clusters, or heatmap.
- Tune the view and save
Set colors, filters, and any proximity limits so the layer stays readable, then save it. Reps can now toggle that layer on the Layers tab and run proximity searches against it.
The records the marker layer plots. A focused report keeps pin counts and load times sensible.
The address or geolocation fields Maps uses to place each pin. Clean, geocoded addresses produce accurate placement.
How pins display: individual markers, clusters, heatmap, or scatter. Choose by data volume and what you want to read at a glance.
Controls who can open Maps and which features they reach. Required before the Maps tab shows for a user.
- Pins are only as good as the address data behind them; ungeocoded or messy addresses place markers in the wrong spot or not at all.
- Maps is a separate paid add-on with its own license, so budget and provisioning are prerequisites, not just configuration.
- Plan around the August 31, 2026 retirement of the standalone Maps mobile app and move field users to the Maps experience in the main Salesforce mobile app.
- Large marker layers can slow the map; use filters, clustering, or proximity limits to cap how many pins render at once.