---
schema_version: "1"
id: df3846722934c012e616718779a654e4bbc187fad62b3ea12f16e067e7f96d12
title: Default vs. Custom Permission Sets for Salesforce Maps
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/salesforce_maps_setup_permissions_sets_considerations.md
canonical_url: https://help.salesforce.com/s/articleView?id=sales.salesforce_maps_setup_permissions_sets_considerations.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 5aa365b4e056d111b41d3240086e84817965e9233445701f1bcd6322c2983c57
description: Salesforce strongly recommends using the default permission sets for most orgs. Salesforce automatically updates default permission sets with every release, so your users always have access to new features without admin intervention.
products:
  - Sales
  - Salesforce Maps
release: "264"
---
# Default vs. Custom Permission Sets for Salesforce Maps

Salesforce strongly recommends using the default permission sets for most orgs. Salesforce automatically updates default permission sets with every release, so your users always have access to new features without admin intervention.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Lightning Experience</strong> and <strong>Salesforce Classic</strong></td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Professional</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</td></tr></tbody></table>

Custom (cloned) permission sets are an edge case. Consider them only if you have specific field-level security requirements that the defaults can't meet. If you do maintain custom permission sets, you manually update them after every release. As schema and object models change with each release, features stop working if the custom permission set isn't kept current.

Default and Custom Permission Sets Decision Guide   
| Question | If yes | If no |
| --- | --- | --- |
| Do you have specific field-level security needs beyond Salesforce defaults? | Consider custom permission sets, but plan for manual maintenance after every release. | Use default permission sets (recommended). |
| Does your team have capacity to review and update permission sets after every release? | Custom is manageable. | Stick with defaults, which update automatically. |
| Did you already clone a permission set in a previous release? | Audit it now—check for missing fields from recent releases. | You're safe with defaults. |
| Are reps suddenly losing access to features after an upgrade? | Your custom set is likely out of date, so re-clone from the latest default. | Not related to this issue. |

#### See Also

- [_Knowledge Article_: Updates to Include in Custom Permission Sets for Salesforce Maps Products](https://help.salesforce.com/s/articleView?id=000395018&type=1&language=en_US)